[JIRA] [timestamper] (JENKINS-23867) Incompatibility with Jenkins 1.572 or later
stevengbrown commented on JENKINS-23867 Incompatibility with Jenkins 1.572 or later OK, here are some things to try: On the project configuration page, make sure the "Add Timestamps to the Console Output" option (found under "Build Environment) is enabled. Check for errors in your web server's log file when running a build and when viewing the console. Attach the contents of the timestamper directory to this JIRA issue. You should see at least two files: "timestamps" and "timestamps.SHA-1". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [next-executions] (JENKINS-23919) show also for poll SCM triggers
Ignacio Albors closed JENKINS-23919 as Duplicate show also for poll SCM triggers See JENKINS-23162 Change By: Ignacio Albors (06/Aug/14 6:26 AM) Status: Open Closed Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-20492) Re-Execute promotion button is gone
Clecio Varjao
edited a comment on JENKINS-20492
Re-Execute promotion button is gone
Can anybody provide with the job/build configuration files? You can create a new dummy job/project with some dummy promotions and send me the the whole project folder (e.g.: %JENKINS_HOME%/jobs/DUMMY-JOB) I have not been able to re-produce this behavior.
you can also use the API:
{baseurl}/view/All/job/{job_name}/config.xml
{baseurl}/view/All/job/{job_name}/promotion/process/{promotion_name}/config.xml
e.g.:
http://localhost/view/All/job/APP-TEST/config.xml
http://localhost/view/All/job/APP-TEST/promotion/process/PROM2/config.xml
What criteria are selected?
[ ] Only when manually approved
[ ] Promote immediately once the build is complete
[ ] Promote immediately once the build is complete based on build parameters
[ ] When the following downstream projects build successfully
[ ] When the following upstream promotions are promoted
The move to the Badge is just technical term. But from the user's perspective, it shouldn't have changed.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [next-executions] (JENKINS-16339) Jobname truncated in next-executions
Ignacio Albors closed JENKINS-16339 as Fixed Jobname truncated in next-executions Change By: Ignacio Albors (06/Aug/14 6:27 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-20492) Re-Execute promotion button is gone
Clecio Varjao
edited a comment on JENKINS-20492
Re-Execute promotion button is gone
Can anybody provide with the job/build configuration files? You can create a new dummy job/project with some dummy promotions and send me the the whole project folder (e.g.: %JENKINS_HOME%/jobs/DUMMY-JOB) I have not been able to re-produce this behavior.
you can also use the API:
{baseurl}/view/All/job/{job_name}/config.xml{baseurl}/view/All/job/{job_name}/promotion/process/{promotion_name}/config.xml
e.g.:
http://localhost/view/All/job/APP-TEST/config.xml
http://localhost/view/All/job/APP-TEST/promotion/process/PROM2/config.xml
What criteria are selected?
[ ] Only when manually approved
[ ] Promote immediately once the build is complete
[ ] Promote immediately once the build is complete based on build parameters
[ ] When the following downstream projects build successfully
[ ] When the following upstream promotions are promoted
The move to the Badge is just technical term. But from the user's perspective, it shouldn't have changed.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-20492) Re-Execute promotion button is gone
Marvi Benedet updated JENKINS-20492 Re-Execute promotion button is gone Change By: Marvi Benedet (06/Aug/14 7:06 AM) Attachment: bug.tgz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-20492) Re-Execute promotion button is gone
Marvi Benedet updated JENKINS-20492 Re-Execute promotion button is gone bug project folder Change By: Marvi Benedet (06/Aug/14 7:10 AM) Attachment: bug.tgz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-20492) Re-Execute promotion button is gone
Marvi Benedet commented on JENKINS-20492 Re-Execute promotion button is gone seems I'm not allowed to upload files here I lost also the commet I wrote. I rewrite it here: Here my job. Note that I'm using AD authentication and there is a user with a numerical ID that is authorized to approve the promotion. This user is also administrator of the whole jenkins, so it can "force the promotions" the only selected criteria is: X Only when manually approved BUT attention: if I promote regularly with the "approve" button all is ok. The problem came only when I use the "force promotion" button. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-24130) Add an option to hide PasswordParameters in build logs
Oleg Nenashev created JENKINS-24130 Add an option to hide PasswordParameters in build logs Issue Type: New Feature Assignee: Gregory Boissinot Components: envinject Created: 06/Aug/14 7:16 AM Description: EnvInject plugin already depends on PasswordParameter in several places in order to hide its values. It would be great to use the plugin in order to hide password parameters in build logs as well. Environment: jenkins-1.509.4 Project: Jenkins Labels: security password Priority: Major Reporter: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-20492) Re-Execute promotion button is gone
Marvi Benedet commented on JENKINS-20492 Re-Execute promotion button is gone I sent you by mail a tgz of a job that show the problem. Bye Marvi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-24130) Add an option to hide PasswordParameters in build logs
Oleg Nenashev started work on JENKINS-24130 Add an option to hide PasswordParameters in build logs Change By: Oleg Nenashev (06/Aug/14 7:24 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-24130) Add an option to hide PasswordParameters in build logs
Oleg Nenashev commented on JENKINS-24130 Add an option to hide PasswordParameters in build logs https://github.com/jenkinsci/envinject-plugin/pull/31 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-24130) Add an option to hide PasswordParameters in build logs
Oleg Nenashev assigned JENKINS-24130 to Oleg Nenashev Add an option to hide PasswordParameters in build logs Change By: Oleg Nenashev (06/Aug/14 7:24 AM) Assignee: GregoryBoissinot OlegNenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-24117) Support for proper shared clients/workspaces
Morne Joubert updated JENKINS-24117 Support for proper shared clients/workspaces I was hoping Jenkins could behave as the diagram shows. From the user perspective the only thing i can think of that would be broken would be the "workspace browser" from the web GUI, but i can live with that. There might be some additional things that needs to be done when cleaning up workspaces. BTW do you know how/when Jenkins cleans up workspaces ? Change By: Morne Joubert (06/Aug/14 7:59 AM) Attachment: Jenkins_shared_workspace.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-24118) Support for P4 TICKETS
Morne Joubert commented on JENKINS-24118 Support for P4 TICKETS I have a test job to show the problem: Building remotely on gb-mlb-pm-002 (linux) in workspace /var/lib/jenkins/workspace/Trigger TOOLS MA_SW_ci_tools Using remote perforce client: Trigger_TOOLS_MA_SW_ci_tools_jenkins_mlb-2062542078 Trigger TOOLS MA_SW_ci_tools $ /u-blox/gallery/perforce/p4/lin_64/2013.3/bin/p4 workspace -o -S //MA_SW/ci_tools Trigger_TOOLS_MA_SW_ci_tools_jenkins_mlb-2062542078 Trigger TOOLS MA_SW_ci_tools $ /u-blox/gallery/perforce/p4/lin_64/2013.3/bin/p4 login -a -p Trigger TOOLS MA_SW_ci_tools $ /u-blox/gallery/perforce/p4/lin_64/2013.3/bin/p4 -P CB36E3E1DC213D9D0161CA6FF7C5309B workspace -o -S //MA_SW/ci_tools Trigger_TOOLS_MA_SW_ci_tools_jenkins_mlb-2062542078 Last build changeset: 50593 Trigger TOOLS MA_SW_ci_tools $ /u-blox/gallery/perforce/p4/lin_64/2013.3/bin/p4 -P CB36E3E1DC213D9D0161CA6FF7C5309B changes -s submitted -m 1 //Trigger_TOOLS_MA_SW_ci_tools_jenkins_mlb-2062542078/... Sync'ing workspace to changelist 50593. Trigger TOOLS MA_SW_ci_tools $ /u-blox/gallery/perforce/p4/lin_64/2013.3/bin/p4 -P CB36E3E1DC213D9D0161CA6FF7C5309B -s sync //Trigger_TOOLS_MA_SW_ci_tools_jenkins_mlb-2062542078/...@50593 Sync complete, took 752 ms Trigger TOOLS MA_SW_ci_tools $ /bin/sh -xe /tmp/hudson3065486592967532870.sh + /u-blox/gallery/perforce/p4/lin_64/2013.3/bin/p4 describe 48315 Perforce password (P4PASSWD) invalid or unset. Build step 'Execute shell' marked build as failure I can see a line: p4 login -a -p Which , according to: http://www.perforce.com/perforce/doc.current/manuals/cmdref/p4_login.html "-p Display the ticket, rather than storing it in the local ticket file." The authentication ticket is then used in later steps: -P CB36E3E1DC213D9D0161CA6FF7C5309B So either the ticket value needs to be exposed to later Job steps can used it via some variable. Or the ticket needs to be stored in a local ticket file. (http://www.perforce.com/perforce/doc.current/manuals/cmdref/P4TICKETS.html) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24131) Make Jenkins SVN Plugin to check whether proxy is working correctly
Artem Krosheninnikov created JENKINS-24131 Make Jenkins SVN Plugin to check whether proxy is working correctly Issue Type: Improvement Assignee: Unassigned Components: subversion Created: 06/Aug/14 9:16 AM Description: SVN plugin can work through proxy, but it doesn't bother whether proxy works or not. Once our proxy wasn't working correctly and the job freezed, doing nothing and leaving console log empty. This time we had some problems with connection (i.e. proxy worked but there were no access to the internet for a limited time) and job failed with such an error: ERROR: Failed to update svn://svn-url-here org.tmatesoft.svn.core.SVNException: svn: E204900: C:\path-to-project-here\ at hudson.scm.subversion.UpdateWithCleanUpdater$TaskImpl$1.handleStatus(UpdateWithCleanUpdater.java:78) at org.tmatesoft.svn.core.wc.SVNStatusClient$1.receive(SVNStatusClient.java:356) at org.tmatesoft.svn.core.wc.SVNStatusClient$1.receive(SVNStatusClient.java:353) at org.tmatesoft.svn.core.wc2.SvnReceivingOperation.receive(SvnReceivingOperation.java:78) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldGetStatus.handleStatus(SvnOldGetStatus.java:37) at org.tmatesoft.svn.core.internal.wc.SVNStatusEditor.sendUnversionedStatus(SVNStatusEditor.java:361) at org.tmatesoft.svn.core.internal.wc.SVNStatusEditor.getDirStatus(SVNStatusEditor.java:209) at org.tmatesoft.svn.core.internal.wc.SVNStatusEditor.handleDirEntry(SVNStatusEditor.java:321) at org.tmatesoft.svn.core.internal.wc.SVNStatusEditor.getDirStatus(SVNStatusEditor.java:256) at org.tmatesoft.svn.core.internal.wc.SVNStatusEditor.closeEdit(SVNStatusEditor.java:114) at org.tmatesoft.svn.core.internal.wc16.SVNStatusClient16.doStatus(SVNStatusClient16.java:430) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldGetStatus.run(SvnOldGetStatus.java:22) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldGetStatus.run(SvnOldGetStatus.java:13) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNStatusClient.doStatus(SVNStatusClient.java:360) at hudson.scm.subversion.UpdateWithCleanUpdater$TaskImpl.preUpdate(UpdateWithCleanUpdater.java:66) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:151) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:161) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:1003) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:984) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:960) at hudson.FilePath.act(FilePath.java:922) at hudson.FilePath.act(FilePath.java:895) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:909) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:844) at hudson.model.AbstractProject.checkout(AbstractProject.java:1254) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:624) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:530) at hudson.model.Run.execute(Run.java:1732) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) Caused by: svn: E204900: C:\path-to-project-here\ at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:109) ... 35 more Caused by: java.nio.file.DirectoryNotEmptyException: C:\path-to-project-here\ at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source) at sun.nio.fs.AbstractFileSystemProvider.delete(Unknown Source) at java.nio.file.Files.delete(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at
[JIRA] [msbuild] (JENKINS-24132) MSBuild Output encoding vs Jenkins' encoding vs Browser Encoding
Hubert Chauvat created JENKINS-24132 MSBuild Output encoding vs Jenkins encoding vs Browser Encoding Issue Type: Improvement Affects Versions: current Assignee: kdsweeney Attachments: Capture.PNG Components: msbuild, mstest Created: 06/Aug/14 9:28 AM Description: When using Jenkins with MSBuild/MSTests, the output console and the plain text have encoding issues. My OS is in French, so we use accents, which are not well displayed in Jenkins' MSBuild/MSTest output (see enclosed) The MS CMD output is said to be encoded in CP 850. My Jenkins/SystemInfo, regarding encoding says : file.encoding Cp1252 file.encoding.pkg sun.io sun.io.unicode.encoding UnicodeLittle sun.java.command C:\Program Files (x86)\Jenkins\jenkins.war --httpPort=8082 --ajp13Port=-1 -Dfile.encoding=UTF-8 sun.jnu.encoding Cp1252 I tried to use the "-Dfile.encoding=" argument with "UTF8","UTF-8", "Cp850" "ISO8859_1" but without any luck. I guess as long as there will be differences between MSDOS/MSBuild's encoding and Jenkins' encoding, I won't be able to have proper outputs. Environment: Win8 in French, Jenkins ver. 1.574, Chrome Version 37.0.2062.58 beta-m Project: Jenkins Priority: Trivial Reporter: Hubert Chauvat This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [msbuild] (JENKINS-24132) MSBuild Output encoding vs Jenkins' encoding vs Browser Encoding
Hubert Chauvat updated JENKINS-24132 MSBuild Output encoding vs Jenkins encoding vs Browser Encoding Change By: Hubert Chauvat (06/Aug/14 9:30 AM) Description: WhenusingJenkinswithMSBuild/MSTests,theoutputconsoleandtheplaintexthaveencodingissues.MyOSisinFrench,soweuseaccents,whicharenotwelldisplayedinJenkinsMSBuild/MSTestoutput(see lastlineinthe enclosed screenshot;thewordGénérationbecameG,n,ration )TheMSCMDoutputissaidtobeencodedin[CP850|http://en.wikipedia.org/wiki/Code_page_850].MyJenkins/SystemInfo,regardingencodingsays: file.encoding Cp1252 file.encoding.pkg sun.io sun.io.unicode.encoding UnicodeLittle sun.java.command C:\ProgramFiles(x86)\Jenkins\jenkins.war--httpPort=8082--ajp13Port=-1-Dfile.encoding=UTF-8 sun.jnu.encoding Cp1252Itriedtousethe-Dfile.encoding=argumentwithUTF8,UTF-8,Cp850ISO8859_1butwithoutanyluck.IguessaslongastherewillbedifferencesbetweenMSDOS/MSBuildsencodingandJenkinsencoding,Iwontbeabletohaveproperoutputs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-21672) Need Pre-send Script to support classpath options
SCM/JIRA link daemon commented on JENKINS-21672 Need Pre-send Script to support classpath options Code changed in jenkins User: Jeff MAURY Path: src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java src/main/java/hudson/plugins/emailext/GroovyScriptPath.java src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/config.groovy src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/global.groovy src/main/webapp/help/globalConfig/defaultClasspath.html src/main/webapp/help/projectConfig/defaultClasspath.html src/test/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptorTest.java src/test/java/hudson/plugins/emailext/ExtendedEmailPublisherTest.java src/test/presend/hudson/plugins/emailext/ExtendedEmailPublisherTestHelper.groovy http://jenkins-ci.org/commit/email-ext-plugin/9c57b9dde50bc8466360bc2e1ba863daaf9c423e Log: Fix JENKINS-21672 - Add classpath for presend script This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23280) Version 1.554.2 broke reverse proxy
René Charbonneau commented on JENKINS-23280 Version 1.554.2 broke reverse proxy Hi Daniel, this might work for mod_proxy, but we still encounter the problem while using mod_jk! And I really don't know what to do. The AllowEncodedSlashes NoDecode option was already set. Can you please tell me what to do if I want to use mod_jk (with https)? Best regards, René This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24133) GIT_BRANCH set to detached when sha1 parameter set in notifyCommit URL
Ian Homer
created JENKINS-24133
GIT_BRANCH set to detached when sha1 parameter set in notifyCommit URL
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
git
Created:
06/Aug/14 11:12 AM
Description:
We recently upgraded our stash install including the stash jenkins webhook. Now in this plugin has recently started calling the Jenkins git notifyCommit endpoint with branches and sha1 query string parameters set in the URL, e.g. it now calls URLs like
/jenkins/git/notifyCommit?url="">
This looks valid according to the Git plugin wiki.
Since this webhook started calling this endpoint with the sha1 parameter our Jenkins jobs has started setting the GIT_BRANCH variable to detached and not the appropriate branch name.
Without this sha1 parameter the job output starts with "Started by an SCM change". With this sha1 parameter the job output starts with e.g. "commit notification b3dd6fe0a7db3b78739cf05c79a85bad56b3bc11".
e.g. Without SHA1 set we see
Started by an SCM change
Building on master in workspace /home/jenkins/jobs/My Job/workspace
/usr/local/bin/git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
/usr/local/bin/git config remote.origin.url ssh://git@my-stash-host:7999/project/repository.git # timeout=10
Fetching upstream changes from ssh://git@my-stash-host:7999/project/repository.git
/usr/local/bin/git --version # timeout=10
/usr/local/bin/git fetch --tags --progress ssh://git@my-stash-host:7999/project/repository.git +refs/heads/*:refs/remotes/origin/*
Seen branch in repository origin/HEAD
Seen branch in repository origin/feature/-1018
Seen branch in repository origin/feature/-1093
...
Seen 293 remote branches
Checking out Revision b3dd6fe0a7db3b78739cf05c79a85bad56b3bc11 (origin/feature/-2571)
e.g. With SHA1 set
commit notification b3dd6fe0a7db3b78739cf05c79a85bad56b3bc11
Building on master in workspace /home/jenkins/jobs/My Job/workspace
/usr/local/bin/git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
/usr/local/bin/git config remote.origin.url ssh://git@my-stash-host:7999/project/repository.git # timeout=10
Fetching upstream changes from ssh://git@my-stash-host:7999/project/repository.git
/usr/local/bin/git --version # timeout=10
/usr/local/bin/git fetch --tags --progress ssh://git@my-stash-host:7999/project/repository.git +refs/heads/*:refs/remotes/origin/*
/usr/local/bin/git rev-parse b3dd6fe0a7db3b78739cf05c79a85bad56b3bc11^{commit} # timeout=10
Checking out Revision b3dd6fe0a7db3b78739cf05c79a85bad56b3bc11(detached)
Note that Checking out Revision line knows the branch (AND sets GIT_BRANCH variable to the correct branch name) without SHA1 set but it does not know the branch, i.e. it says detached for the branch name (AND sets GIT_BRANCH to detached).
Note we have implemented a work around in apache by removing the sha1 parameter from the URL which fixes this for our environment (how we don't benefit from the notifyCommit being explicit about the commit revision to build).
FYI - our Apache configuration workaround is:
RewriteEngine On
# Remove branches and sha1 from notify notifyCommit calls
RewriteCond %{QUERY_STRING} ^url="" [NC]
RewriteRule ^ %{REQUEST_URI}?url="" [PT]
Project:
Jenkins
Priority:
Major
Reporter:
Ian Homer
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] [git] (JENKINS-24133) GIT_BRANCH set to detached when sha1 parameter set in notifyCommit URL
Ian Homer
updated JENKINS-24133
GIT_BRANCH set to detached when sha1 parameter set in notifyCommit URL
Change By:
Ian Homer
(06/Aug/14 11:15 AM)
Description:
Werecentlyupgradedourstashinstallincludingthestashjenkinswebhook.Nowinthisplugin[hasrecentlystartedcalling|https://github.com/Nerdwin15/stash-jenkins-postreceive-webhook/commit/d4c9709557504c72473210c413592827b5460f0f]theJenkinsgit*notifyCommit*endpointwith*branches*and*sha1*querystringparameterssetintheURL,e.g.itnowcallsURLslike/jenkins/git/notifyCommit?url="">Thislooksvalidaccordingtothe[Gitpluginwiki|https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin].
ItusedtoNOTsetthebranchesandsha1parameter,e.g.simply.../jenkins/git/notifyCommit?url="">
Sincethiswebhookstartedcallingthisendpointwiththesha1parameterourJenkinsjobshasstartedsettingtheGIT_BRANCHvariabletodetachedandnottheappropriatebranchname.Withoutthissha1parameterthejoboutputstartswithStartedbyanSCMchange.Withthissha1parameterthejoboutputstartswithe.g.commitnotificationb3dd6fe0a7db3b78739cf05c79a85bad56b3bc11.e.g.WithoutSHA1setwesee{code}StartedbyanSCMchangeBuildingonmasterinworkspace/home/jenkins/jobs/MyJob/workspace/usr/local/bin/gitrev-parse--is-inside-work-tree#timeout=10FetchingchangesfromtheremoteGitrepository/usr/local/bin/gitconfigremote.origin.urlssh://git@my-stash-host:7999/project/repository.git#timeout=10Fetchingupstreamchangesfromssh://git@my-stash-host:7999/project/repository.git/usr/local/bin/git--version#timeout=10/usr/local/bin/gitfetch--tags--progreh://git@my-stash-host:7999/project/repository.git+refs/heads/*:refs/remotes/origin/*Seenbranchinrepositoryorigin/HEADSeenbranchinrepositoryorigin/feature/-1018Seenbranchinrepositoryorigin/feature/-1093...Seen293remotebranchesCheckingoutRevisionb3dd6fe0a7db3b78739cf05c79a85bad56b3bc11(origin/feature/-2571){code}e.g.WithSHA1set{code}commitnotificationb3dd6fe0a7db3b78739cf05c79a85bad56b3bc11Buildingonmasterinworkspace/home/jenkins/jobs/MyJob/workspace/usr/local/bin/gitrev-parse--is-inside-work-tree#timeout=10FetchingchangesfromtheremoteGitrepository/usr/local/bin/gitconfigremote.origin.urlssh://git@my-stash-host:7999/project/repository.git#timeout=10Fetchingupstreamchangesfromssh://git@my-stash-host:7999/project/repository.git/usr/local/bin/git--version#timeout=10/usr/local/bin/gitfetch--tags--progreh://git@my-stash-host:7999/project/repository.git+refs/heads/*:refs/remotes/origin/*/usr/local/bin/gitrev-parseb3dd6fe0a7db3b78739cf05c79a85bad56b3bc11^{commit}#timeout=10CheckingoutRevisionb3dd6fe0a7db3b78739cf05c79a85bad56b3bc11(detached){code}NotethatCheckingoutRevisionlineknowsthebranch(ANDsetsGIT_BRANCHvariabletothecorrectbranchname)withoutSHA1setbutitdoesnotknowthebranch,i.e.itsets*detached*forthebranchname(ANDsetsGIT_BRANCHtodetached).Notewehaveimplementedaworkaroundinapachebyremovingthesha1parameterfromtheURLwhichfixesthisforourenvironment(howwedontbenefitfromthenotifyCommitbeingexplicitaboutthecommitrevisiontobuild).FYI-ourApacheconfigurationworkaroundis:{code}RewriteEngineOn#Removebranchesandsha1fromnotifynotifyCommitcallsRewriteCond%{QUERY_STRING}^url="">RewriteRule^%{REQUEST_URI}?url="">{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24133) GIT_BRANCH set to detached when sha1 parameter set in notifyCommit URL
Ian Homer
updated JENKINS-24133
GIT_BRANCH set to detached when sha1 parameter set in notifyCommit URL
Change By:
Ian Homer
(06/Aug/14 11:13 AM)
Description:
Werecentlyupgradedourstashinstallincludingthestashjenkinswebhook.Nowinthisplugin[hasrecentlystartedcalling|https://github.com/Nerdwin15/stash-jenkins-postreceive-webhook/commit/d4c9709557504c72473210c413592827b5460f0f]theJenkinsgit*notifyCommit*endpointwith*branches*and*sha1*querystringparameterssetintheURL,e.g.itnowcallsURLslike/jenkins/git/notifyCommit?url="">Thislooksvalidaccordingtothe[Gitpluginwiki|https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin].Sincethiswebhookstartedcallingthisendpointwiththesha1parameterourJenkinsjobshasstartedsettingtheGIT_BRANCHvariabletodetachedandnottheappropriatebranchname.Withoutthissha1parameterthejoboutputstartswithStartedbyanSCMchange.Withthissha1parameterthejoboutputstartswithe.g.commitnotificationb3dd6fe0a7db3b78739cf05c79a85bad56b3bc11.e.g.WithoutSHA1setwesee{code}StartedbyanSCMchangeBuildingonmasterinworkspace/home/jenkins/jobs/MyJob/workspace/usr/local/bin/gitrev-parse--is-inside-work-tree#timeout=10FetchingchangesfromtheremoteGitrepository/usr/local/bin/gitconfigremote.origin.urlssh://git@my-stash-host:7999/project/repository.git#timeout=10Fetchingupstreamchangesfromssh://git@my-stash-host:7999/project/repository.git/usr/local/bin/git--version#timeout=10/usr/local/bin/gitfetch--tags--progreh://git@my-stash-host:7999/project/repository.git+refs/heads/*:refs/remotes/origin/*Seenbranchinrepositoryorigin/HEADSeenbranchinrepositoryorigin/feature/-1018Seenbranchinrepositoryorigin/feature/-1093...Seen293remotebranchesCheckingoutRevisionb3dd6fe0a7db3b78739cf05c79a85bad56b3bc11(origin/feature/-2571){code}e.g.WithSHA1set{code}commitnotificationb3dd6fe0a7db3b78739cf05c79a85bad56b3bc11Buildingonmasterinworkspace/home/jenkins/jobs/MyJob/workspace/usr/local/bin/gitrev-parse--is-inside-work-tree#timeout=10FetchingchangesfromtheremoteGitrepository/usr/local/bin/gitconfigremote.origin.urlssh://git@my-stash-host:7999/project/repository.git#timeout=10Fetchingupstreamchangesfromssh://git@my-stash-host:7999/project/repository.git/usr/local/bin/git--version#timeout=10/usr/local/bin/gitfetch--tags--progreh://git@my-stash-host:7999/project/repository.git+refs/heads/*:refs/remotes/origin/*/usr/local/bin/gitrev-parseb3dd6fe0a7db3b78739cf05c79a85bad56b3bc11^{commit}#timeout=10CheckingoutRevisionb3dd6fe0a7db3b78739cf05c79a85bad56b3bc11(detached){code}NotethatCheckingoutRevisionlineknowsthebranch(ANDsetsGIT_BRANCHvariabletothecorrectbranchname)withoutSHA1setbutitdoesnotknowthebranch,i.e.it
says
sets
*detached*forthebranchname(ANDsetsGIT_BRANCHtodetached).Notewehaveimplementedaworkaroundinapachebyremovingthesha1parameterfromtheURLwhichfixesthisforourenvironment(howwedontbenefitfromthenotifyCommitbeingexplicitaboutthecommitrevisiontobuild).FYI-ourApacheconfigurationworkaroundis:{code}RewriteEngineOn#Removebranchesandsha1fromnotifynotifyCommitcallsRewriteCond%{QUERY_STRING}^url="">RewriteRule^%{REQUEST_URI}?url="">{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24133) GIT_BRANCH set to detached when sha1 parameter set in notifyCommit URL
Ian Homer
updated JENKINS-24133
GIT_BRANCH set to detached when sha1 parameter set in notifyCommit URL
Change By:
Ian Homer
(06/Aug/14 11:16 AM)
Description:
Werecentlyupgradedourstashinstallincludingthestashjenkinswebhook.Nowinthisplugin[hasrecentlystartedcalling|https://github.com/Nerdwin15/stash-jenkins-postreceive-webhook/commit/d4c9709557504c72473210c413592827b5460f0f]theJenkinsgit*notifyCommit*endpointwith*branches*and*sha1*querystringparameterssetintheURL,e.g.itnowcallsURLslike/jenkins/git/notifyCommit?url="">Thislooksvalidaccordingtothe[Gitpluginwiki|https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin].ItusedtoNOTsetthebranchesandsha1parameter,e.g.simply.../jenkins/git/notifyCommit?url="">Sincethiswebhookstartedcallingthisendpointwiththesha1parameterourJenkinsjobshasstartedsettingtheGIT_BRANCHvariabletodetachedandnottheappropriatebranchname.Withoutthissha1parameterthejoboutputstartswithStartedbyanSCMchange.Withthissha1parameterthejoboutputstartswithe.g.commitnotificationb3dd6fe0a7db3b78739cf05c79a85bad56b3bc11.e.g.WithoutSHA1setwesee{code}StartedbyanSCMchangeBuildingonmasterinworkspace/home/jenkins/jobs/MyJob/workspace/usr/local/bin/gitrev-parse--is-inside-work-tree#timeout=10FetchingchangesfromtheremoteGitrepository/usr/local/bin/gitconfigremote.origin.urlssh://git@my-stash-host:7999/project/repository.git#timeout=10Fetchingupstreamchangesfromssh://git@my-stash-host:7999/project/repository.git/usr/local/bin/git--version#timeout=10/usr/local/bin/gitfetch--tags--progreh://git@my-stash-host:7999/project/repository.git+refs/heads/*:refs/remotes/origin/*Seenbranchinrepositoryorigin/HEADSeenbranchinrepositoryorigin/feature/-1018Seenbranchinrepositoryorigin/feature/-1093...Seen293remotebranchesCheckingoutRevisionb3dd6fe0a7db3b78739cf05c79a85bad56b3bc11(origin/feature/-2571){code}e.g.WithSHA1set{code}commitnotificationb3dd6fe0a7db3b78739cf05c79a85bad56b3bc11Buildingonmasterinworkspace/home/jenkins/jobs/MyJob/workspace/usr/local/bin/gitrev-parse--is-inside-work-tree#timeout=10FetchingchangesfromtheremoteGitrepository/usr/local/bin/gitconfigremote.origin.urlssh://git@my-stash-host:7999/project/repository.git#timeout=10Fetchingupstreamchangesfromssh://git@my-stash-host:7999/project/repository.git/usr/local/bin/git--version#timeout=10/usr/local/bin/gitfetch--tags--progreh://git@my-stash-host:7999/project/repository.git+refs/heads/*:refs/remotes/origin/*/usr/local/bin/gitrev-parseb3dd6fe0a7db3b78739cf05c79a85bad56b3bc11^{commit}#timeout=10CheckingoutRevisionb3dd6fe0a7db3b78739cf05c79a85bad56b3bc11(detached){code}NotethatCheckingoutRevisionlineknowsthebranch(ANDsetsGIT_BRANCHvariabletothecorrectbranchname)withoutSHA1setbutitdoesnotknowthebranch,i.e.itsets*detached*forthebranchname(ANDsetsGIT_BRANCHtodetached).Notewehaveimplementedaworkaroundinapachebyremovingthesha1parameterfromtheURLwhichfixesthisforourenvironment(
how
however
wedontbenefitfromthenotifyCommitbeingexplicitaboutthecommitrevisiontobuild).FYI-ourApacheconfigurationworkaroundis:{code}RewriteEngineOn#Removebranchesandsha1fromnotifynotifyCommitcallsRewriteCond%{QUERY_STRING}^url="">RewriteRule^%{REQUEST_URI}?url="">{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-auth] (JENKINS-24134) Make environment variables available for matrix-based security plugin
Max Krause
created JENKINS-24134
Make environment variables available for matrix-based security plugin
Issue Type:
Improvement
Affects Versions:
current
Assignee:
Jesse Glick
Attachments:
matrix_auth_1.jpg
Components:
matrix-auth
Created:
06/Aug/14 11:19 AM
Description:
The matrix-auth plugin only supports user names. It would be an useful improvement to support environment variables like ${BUILD_USER_ID}, to automatically assign permissions to the user who started the build, respectively to enter the variable in the configuration of a jobgenerator and replace it with the username in the generated job.
Environment:
Windows 7 Enterprise 64-Bit, JDK 1.7.0_60
Project:
Jenkins
Labels:
plugin
jenkins
security
matrix
matrix-auth
Priority:
Major
Reporter:
Max Krause
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-23160) Newly added module locations' / additional credentials' Add credential button does not work
SCM/JIRA link daemon resolved JENKINS-23160 as Fixed Newly added module locations / additional credentials Add credential button does not work Change By: SCM/JIRA link daemon (06/Aug/14 11:22 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-23160) Newly added module locations' / additional credentials' Add credential button does not work
SCM/JIRA link daemon commented on JENKINS-23160 Newly added module locations / additional credentials Add credential button does not work Code changed in jenkins User: Stephen Connolly Path: src/main/resources/lib/credentials/select.jelly src/main/resources/lib/credentials/select/select.css src/main/resources/lib/credentials/select/select.js http://jenkins-ci.org/commit/credentials-plugin/7c263cbb86276cf9a7ff67c43d6532776efac5aa Log: FIXED JENKINS-23160 Newly added module locations' / additional credentials' "Add" credential button does not work Also changed the width of the drop-down to be auto so that the add button is more clearly associated Also fixed select box alignment with add button Note: Root cause was f:repeatable was neither generating a new id nor re-executing the in-line script, this fixes both in one go by using Behaviour to apply the rule thus removing the need for the id on the button This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [project-inheritance] (JENKINS-22885) Creation of Inheritance Project throws Exception
Asmund Ostvold commented on JENKINS-22885 Creation of Inheritance Project throws Exception I observe the same issue with Jenkins ver. 1.565.1 and 1.5.3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
Thomas Lehmann commented on JENKINS-14276 Git SCM-polling doesnt work when using a parametrized branch-name We have the same problem: Jenkins 1.572, Git Plugin 2.2.1 and Git Client Plugin 1.8.0 When I remove the variables from the branch field writing the branch name directly there the polling stops. Additionally I would like to know how to solve the upgrade problem. We have a Centos 6 with Git installed by the package manager being the version 1.7.1. The plugin section says for upgrading the Git Plugin: "This plugin allows use of Git as a build SCM. A recent Git runtime is required (1.7.9 minimum, 1.8.x recommended). Plugin is only tested on official git client. Use exotic installations at your own risks." This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20815) Show Failed Status While the Build is Still In Progress
Pim Verkerk commented on JENKINS-20815 Show Failed Status While the Build is Still In Progress I have the same issue on jenkins ver. 1.548. I could not find any issues with shared workspaces. My best guess is a hiccup in the connection between master/slave. Maybe this causes some issues on the master when deciding the status of a job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovyaxis] (JENKINS-24135) Use groovy-sandbox to avoid the impact on the system stability
Oleg Nenashev created JENKINS-24135 Use groovy-sandbox to avoid the impact on the system stability Issue Type: Bug Assignee: emanuelez Components: groovyaxis Created: 06/Aug/14 11:44 AM Description: Currently, any user can call System.exit() from the plugin (just click on the test button) = any user with job configure permissions may stop the Jenkins instance. Project: Jenkins Priority: Major Reporter: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovyaxis] (JENKINS-24135) Use groovy-sandbox to avoid the impact on the system stability
Oleg Nenashev updated JENKINS-24135 Use groovy-sandbox to avoid the impact on the system stability Change By: Oleg Nenashev (06/Aug/14 11:45 AM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovyaxis] (JENKINS-24135) Use groovy-sandbox to avoid the impact on the system stability
Oleg Nenashev updated JENKINS-24135 Use groovy-sandbox to avoid the impact on the system stability "Test" axis = service dies on the check Change By: Oleg Nenashev (06/Aug/14 11:48 AM) Attachment: JENKINS-24135.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-21672) Need Pre-send Script to support classpath options
Jeff MAURY assigned JENKINS-21672 to Jeff MAURY Need Pre-send Script to support classpath options Change By: Jeff MAURY (06/Aug/14 12:02 PM) Assignee: AlexEarl JeffMAURY This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-16532) ${CHANGES} token does not give any output for debugging or any No Changes response when there are no changes like the web page
Jeff MAURY
resolved JENKINS-16532 as Fixed
${CHANGES} token does not give any output for debugging or any No Changes response when there are no changes like the web page
Change By:
Jeff MAURY
(06/Aug/14 12:05 PM)
Status:
Open
Resolved
Resolution:
Fixed
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-auth] (JENKINS-24134) Make environment variables available for matrix-based security plugin
Max Krause
updated JENKINS-24134
Make environment variables available for matrix-based security plugin
Change By:
Max Krause
(06/Aug/14 12:05 PM)
Description:
Thematrix-authpluginonlysupportsusernames.Itwouldbeanusefulimprovementtosupportenvironmentvariableslike${BUILD_USER_ID},toautomaticallyassignpermissionstotheuserwhostartedthebuild,respectivelytoenterthevariableintheconfigurationofajobgeneratorandreplaceitwiththeusernameinthe
configurationofthe
generatedjob.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [accurev] (JENKINS-22805) Version .6.22 prompts for ACCUREV_CLIENT_PATH with job rebuilder plugin
Walter Kacynski closed JENKINS-22805 as Fixed Version .6.22 prompts for ACCUREV_CLIENT_PATH with job rebuilder plugin Change By: Walter Kacynski (06/Aug/14 12:06 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [accurev] (JENKINS-22765) configuring a job shows an accurev syntax output in the master
Walter Kacynski updated JENKINS-22765 configuring a job shows an accurev syntax output in the master This causes the masters' log to get very polluted with information that doesn't matter. Change By: Walter Kacynski (06/Aug/14 12:08 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-auth] (JENKINS-24134) Make environment variables available for Matrix Authorization Strategy Plugin
Max Krause
updated JENKINS-24134
Make environment variables available for Matrix Authorization Strategy Plugin
Change By:
Max Krause
(06/Aug/14 12:10 PM)
Summary:
Makeenvironmentvariablesavailablefor
matrix-basedsecurityplugin
MatrixAuthorizationStrategyPlugin
Description:
Thematrix-authpluginonlysupportsusernames.Itwouldbeanusefulimprovementtosupportenvironmentvariableslike${BUILD_USER_ID},toautomaticallyassignpermissionstotheuserwhostartedthebuild,
respectively
ormorespecifically
toenterthevariableintheconfigurationofajobgeneratorandreplaceitwiththeusername
oftheuserwhostartedthejobgenerator
intheconfigurationof
the
a
generatedjob.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [accurev] (JENKINS-21496) Version .6.22 removes advanced options for AccuRev Servers in Global configuration
Walter Kacynski commented on JENKINS-21496 Version .6.22 removes advanced options for AccuRev Servers in Global configuration Please publish this change to the update center as an official release. I have been using the snapshot version and it works nicely. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [accurev] (JENKINS-13817) Jenkins Displays Accurev Password in Logs
Walter Kacynski updated JENKINS-13817 Jenkins Displays Accurev Password in Logs Change By: Walter Kacynski (06/Aug/14 12:10 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [accurev] (JENKINS-10209) AccuRev plugin should work around accurev's spontaneous logout behaviour
Walter Kacynski commented on JENKINS-10209 AccuRev plugin should work around accurevs spontaneous logout behaviour Version .6.27-SNAPSHOT allows you to select the "Minimize Login" option and this causes an accurev info command to be used to see if the users is logged in. This should address the concern for this problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [accurev] (JENKINS-10209) AccuRev plugin should work around accurev's spontaneous logout behaviour
Walter Kacynski resolved JENKINS-10209 as Fixed AccuRev plugin should work around accurevs spontaneous logout behaviour Change By: Walter Kacynski (06/Aug/14 12:13 PM) Status: Open Resolved Assignee: ScottTatum pjdarton Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-auth] (JENKINS-24134) Make environment variables available for Matrix Authorization Strategy Plugin
Max Krause
updated JENKINS-24134
Make environment variables available for Matrix Authorization Strategy Plugin
Change By:
Max Krause
(06/Aug/14 12:12 PM)
Description:
Thematrix-authpluginonlysupportsusernames.Itwouldbeanusefulimprovementtosupportenvironmentvariableslike${BUILD_USER_ID},toautomaticallyassignpermissionstotheuserwhostartedthebuild,ormorespecificallytoenterthevariableintheconfigurationofajobgeneratorandreplaceitwiththeusernameoftheuserwhostartedthejobgeneratorintheconfigurationof
a
the
generated
job
jobs
.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [slave-status] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
Kevin Browder commented on JENKINS-22932 Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted @Andy did you happen to see if there were any jobs that were running at the time that died? If so did the jobs have a line containing "Caused by: java.nio.channels.ClosedChannelException" (what this issue looks to have fixed) or "Caused by: java.nio.channels.ClosedChannelException" (issue I raised in JENKINS-24050); basically the slave log doesn't really tell you enough information for these two issues. Additionally did your other JNLP slaves disconnect? If none of the above are true then I think what you've got might be a different issue than this or JENKINS-24050 (and I guess it should be filled separately). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-21672) Need Pre-send Script to support classpath options
SCM/JIRA link daemon commented on JENKINS-21672 Need Pre-send Script to support classpath options Code changed in jenkins User: Jeff MAURY Path: src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java http://jenkins-ci.org/commit/email-ext-plugin/21e066a5e1363115343226734765dca063ff1f11 Log: Fix JENKINS-21672 - Removed dummy debug code This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24050) All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting
Kevin Browder commented on JENKINS-24050 All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting If it wasn't clear (re-reading my last message I guess it wasn't); yes this represents a different variant to issue initially presented in JENKINS-22932, basically a different exception get's thrown which I think I've fixed in the pull request above, it's probably possible to refactor the fix for both issues in such a way that other exceptions don't kill the main NIO/select loop in the future but this specific issue can be fixed without that (it's easier for you guys to review this anyways). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial] (JENKINS-24136) Add support for build/release tagging with bookmarks
Justinas Urbanavicius created JENKINS-24136 Add support for build/release tagging with bookmarks Issue Type: New Feature Assignee: Jesse Glick Components: mercurial Created: 06/Aug/14 12:48 PM Description: Would be nice if mercurial plugin could add a biuld action, that would bookmark a successful build with specified version number, like build number, from jenkins environment variables and push to the repository. that way after a build we could see by the bookmark in repository witch revision was build, which revision is the current release. Project: Jenkins Labels: tag bookmarks release build-action Priority: Major Reporter: Justinas Urbanavicius This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-20073) Add an action to allow moving credentials between credential domains
SCM/JIRA link daemon resolved JENKINS-20073 as Fixed Add an action to allow moving credentials between credential domains Change By: SCM/JIRA link daemon (06/Aug/14 12:59 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-20073) Add an action to allow moving credentials between credential domains
SCM/JIRA link daemon commented on JENKINS-20073 Add an action to allow moving credentials between credential domains Code changed in jenkins User: Stephen Connolly Path: src/images/move.svg src/main/java/com/cloudbees/plugins/credentials/CredentialsStoreAction.java src/main/resources/com/cloudbees/plugins/credentials/CredentialsStoreAction/CredentialsWrapper/move.jelly src/main/resources/com/cloudbees/plugins/credentials/CredentialsStoreAction/CredentialsWrapper/move.properties src/main/resources/com/cloudbees/plugins/credentials/CredentialsStoreAction/CredentialsWrapper/sidepanel.jelly src/main/resources/com/cloudbees/plugins/credentials/CredentialsStoreAction/CredentialsWrapper/update.jelly src/main/resources/com/cloudbees/plugins/credentials/CredentialsStoreAction/DomainWrapper/configure.jelly src/main/resources/com/cloudbees/plugins/credentials/CredentialsStoreAction/DomainWrapper/newCredentials.jelly src/main/resources/com/cloudbees/plugins/credentials/CredentialsStoreAction/newDomain.jelly src/main/webapp/images/16x16/move.png src/main/webapp/images/24x24/move.png src/main/webapp/images/32x32/move.png src/main/webapp/images/48x48/move.png http://jenkins-ci.org/commit/credentials-plugin/3d9ee73a1e037b0b9429a0b955ff1e2b34b2389a Log: FIXED JENKINS-20073 Add an action to allow moving credentials between credential domains This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [accurev] (JENKINS-10209) AccuRev plugin should work around accurev's spontaneous logout behaviour
pjdarton commented on JENKINS-10209 AccuRev plugin should work around accurevs spontaneous logout behaviour FYI, there was "minimise login" behavior added by JENKINS-8935, which was incorporated in 0.6.15 a long time ago, well before 0.6.27, but this issue isn't the same as that issue. i.e. the plugin checked (using accurev info) whether or not the user is logged in, and then only logged in if the user isn't logged in already. However, that algorithm doesn't address this issue (which is why this issue was raised separately). This issue is all about the way the accurev server can spontaneously log you out in between accurev client commands - doing a pre-emptive "if accurev info says you're not logged in, then log in" at the start isn't enough - one needs to trap the "you're not logged in" errors from every accurev command that is done. e.g. if the sequence is as follows: accurev info if not logged in, log in accurev show ... streams accurev mksnap ... accurev pop ... then the code needs to check that the "accurev show", "accurev mksnap" and "accurev pop" commands didn't complain that the user wasn't logged in (and then login and re-issue the command if that's the case), as the login that was checked for right at the start can spontaneously expire at any point. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slave-status] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
Andy Pham commented on JENKINS-22932 Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted Kevin, I haven't had a chance to catch the issue when a job is running yet and things still seem working since my last Jenkins restart. I'll keep an eye out for it. It could be a different problem and once I'm able to confirm that I'll log a different defect. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-24117) Support for proper shared clients/workspaces
Rob Petti commented on JENKINS-24117 Support for proper shared clients/workspaces Executors cannot have their own separate workspace, as far as I know. The workspace location is configurable from the job level and the slave level, executors are not individually configurable. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-24118) Support for P4 TICKETS
Rob Petti commented on JENKINS-24118 Support for P4 TICKETS It's exposed in P4TICKET. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [accurev] (JENKINS-10209) AccuRev plugin should work around accurev's spontaneous logout behaviour
Walter Kacynski commented on JENKINS-10209 AccuRev plugin should work around accurevs spontaneous logout behaviour Why not use the non-expiring login option? We haven't experienced this type of problem when using the non-expiring option. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [timestamper] (JENKINS-23867) Incompatibility with Jenkins 1.572 or later
A. Kirby commented on JENKINS-23867 Incompatibility with Jenkins 1.572 or later Thanks Steve. I don't recall checking this in the previous releases and I didn't think to look at the project configuration to enable the plugin, but that's what the problem was. The "Add Timestamps to the Console Output" wasn't checked. Things are working now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-24117) Support for proper shared clients/workspaces
Morne Joubert
commented on JENKINS-24117
Support for proper shared clients/workspaces
When a job start there is a variable ${EXECUTOR_NUMBER} that indicated the current executor that is going to perform the work.
https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project
Since we know ${EXECUTOR_NUMBER} when a job starts, any reason we can't can set the workspace and client spec dynamically ?
When you run a multiple instances of a job in Jenkins the default behaviour is to add a @n (etc @2 for the 2nd executor), automatically to the workspace (and p4 client spec)
So Jenkins already handles different workspaces for different executors.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [timestamper] (JENKINS-23867) Incompatibility with Jenkins 1.572 or later
stevengbrown resolved JENKINS-23867 as Fixed Incompatibility with Jenkins 1.572 or later Great. Happy to help. Change By: stevengbrown (06/Aug/14 2:12 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-24117) Support for proper shared clients/workspaces
Rob Petti commented on JENKINS-24117 Support for proper shared clients/workspaces The concurrent workspace functionality does not take its number from the executor. It has nothing to do with it. That being said, have you tried simply relying on the concurrency functionality that's already there? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-24118) Support for P4 TICKETS
Morne Joubert commented on JENKINS-24118 Support for P4 TICKETS Ah, is is exposed as a env variable didn't pick that up, sorry. Just tried it. adding -P $P4TICKET to the beginning of my commands worked. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ui-changes] (JENKINS-24128) BUILD Button overlaps onto Build history window
Daniel Beck commented on JENKINS-24128 BUILD Button overlaps onto Build history window Could you please show the rest of the page? Which version of Jenkins is this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [appaloosa] (JENKINS-24137) Bad help blocks displayed on description and groups fields
Mickael Morier created JENKINS-24137 Bad help blocks displayed on description and groups fields Issue Type: Bug Assignee: Unassigned Attachments: Capture d’écran 2014-08-06 à 16.16.25.png Components: appaloosa Created: 06/Aug/14 2:24 PM Description: As you can see in screenshot attached, help block of description field is linked to groups field. In return, help block of groups field is linked to description one. Project: Jenkins Priority: Trivial Reporter: Mickael Morier This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ant] (JENKINS-24138) Archived file names can change when moved from slave to master
Chris Rees created JENKINS-24138 Archived file names can change when moved from slave to master Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: JapaneseName.png, JapaneseNameBroken.png, Output.png Components: ant Created: 06/Aug/14 2:30 PM Description: I have a Jenkins set up that uses slaves and archives files after a build. What I've found is that if there is a file that uses multi-byte characters in the name (like 日本語ファイル) then the name gets altered when uploaded to the Jenkins master. Using the master node does not have the issue, so I did some research and found that the problem actually lies in the version of Ant that is being used (1.8.3) and how it reads file names and converts the multi-byte characters down to one byte. It looks like the issue was fixed in Apache Ant 1.9.0 Environment: Tested on Ubuntu and RHEL6. Currently using Jenkins 1.553 but the issue would be present in all current versions Project: Jenkins Labels: ant tar slave archive artifact Priority: Major Reporter: Chris Rees This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24138) Archived file names can change when moved from slave to master
Daniel Beck updated JENKINS-24138 Archived file names can change when moved from slave to master Setting file.encoding system property has no effect? Change By: Daniel Beck (06/Aug/14 2:33 PM) Affects Version/s: current Component/s: core Component/s: ant This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-24117) Support for proper shared clients/workspaces
Morne Joubert
commented on JENKINS-24117
Support for proper shared clients/workspaces
ah, i must have read a JIRA ticket wrong then.
My problem is not that i can't run things concurrent.
My issue is that i have to sync to a stream 100 times for 100 builds that use the same stream.
Thanks for your help, i am going to prototype a pre SCM step that does the following
1) Detects the ${EXECUTOR_NUMBER}
2) Uses a variable for specifying a stream and creates a P4 client spec pointing to a unique workspace
3) Pass the new generated (or use one if already exists) to the P4 plugin and tick the boxes to use an existing client spec and not modify it
I will give that a go and let you know.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24138) Archived file names can change when moved from slave to master
Chris Rees commented on JENKINS-24138 Archived file names can change when moved from slave to master I tried setting the file.encoding property and it didn't change anything. The issue looked like it was in TarEntry and TarUtils within Ant when digging down to see why file names were being modified. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-20966) SSH CLI -s option does not report Started jobname #58 until job finishes
SCM/JIRA link daemon commented on JENKINS-20966 SSH CLI -s option does not report Started jobname #58 until job finishes Code changed in jenkins User: Nicolas De Loof Path: core/src/main/java/hudson/cli/BuildCommand.java http://jenkins-ci.org/commit/jenkins/eeebfee5d895dc27b46a77d1651b3d9d06a6bccc Log: FIXED JENKINS-20966 flush output so cli get the build number being started This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-20966) SSH CLI -s option does not report Started jobname #58 until job finishes
Walter Kacynski assigned JENKINS-20966 to Walter Kacynski SSH CLI -s option does not report Started jobname #58 until job finishes Change By: Walter Kacynski (06/Aug/14 2:43 PM) Assignee: WalterKacynski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24138) Archived file names can change when moved from slave to master
Chris Rees commented on JENKINS-24138 Archived file names can change when moved from slave to master I should probably add in that the Jenkins server is being run in WebSphere Liberty Profile 8.5.5.2 and Java is an IBM 1.6.0. We tracked the issue down to TarUtils by debugging the running Jenkins server WLP Info (dev machine): ps aux | grep wlp crr 1460 0.0 0.0 780 ?S10:37 0:00 /bin/sh /opt/ibm/wlp/bin/server run Home crr 1523 53.7 2.1 4906124 343144 ? Sl 10:37 1:00 /usr/lib/j2sdk1.6-ibm/jre/bin/java -XX:MaxPermSize=256m -Darchaius.deployment.applicationId=pipeline -Darchaius.deployment.environment=dev -Darchaius.dynamicPropertyFactory.registerConfigWithJMX=true -Xdebug -Xrunjdwp:transport=dt_socket,address=localhost:1,server=y,suspend=n -Dcom.sun.management.jmxremote -Dfile.encoding=UTF-8 -Xquickstart -Dwas4d.error.page=localhost:2425/108267124 -javaagent:/opt/ibm/wlp/bin/tools/ws-javaagent.jar -jar /opt/ibm/wlp/bin/tools/ws-server.jar Home Java: java version "1.6.0" Java(TM) SE Runtime Environment (build pxa6460sr16-20140418_01(SR16)) IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr16-20140416_196573 (JIT enabled, AOT enabled) J9VM - 20140416_196573 JIT - r9_20130920_46510ifx5 GC - GA24_Java6_SR16_20140416_1614_B196573) JCL - 20140406_01 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24138) Archived file names can change when moved from slave to master
Chris Rees updated JENKINS-24138 Archived file names can change when moved from slave to master Change By: Chris Rees (06/Aug/14 2:44 PM) Environment: TestedonUbuntuandRHEL6.CurrentlyusingJenkins1.553buttheissuewouldbepresentinallcurrentversions .TheserverrunsinWebSphereLibertyProfile8.5.5.1and8.5.5.2andJavaisanIBMJDK1.6.0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [accurev] (JENKINS-10209) AccuRev plugin should work around accurev's spontaneous logout behaviour
pjdarton commented on JENKINS-10209 AccuRev plugin should work around accurevs spontaneous logout behaviour Because the "non-expiring" login option doesn't prevent the accurev client from behaving as if the login has expired (for all the reasons set out in the first paragraph of the original problem report). Personally, I'd call this a bug in accurev. Accurev call it a "feature" of their authentication method In practice, as you correctly point out, if one uses non-expiring logins then things expire infrequently enough that you're unlikely to get "unauthenticated" twice in rapid succession, but it can (and, IME, has) occurred, just not enough for it to be a major blocking issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-16416) EXCEPTION_ACCESS_VIOLATION uninstalling Active Directory plugin with GUI
Walter Kacynski closed JENKINS-16416 as Incomplete EXCEPTION_ACCESS_VIOLATION uninstalling Active Directory plugin with GUI This is so old and the AD plugin has had many updates since this time. Change By: Walter Kacynski (06/Aug/14 2:49 PM) Status: Open Closed Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [accurev] (JENKINS-10209) AccuRev plugin should work around accurev's spontaneous logout behaviour
Walter Kacynski commented on JENKINS-10209 AccuRev plugin should work around accurevs spontaneous logout behaviour In that case, I'm not really sure how the plugin is suppose to address this problem and it sounds like this bug would be better handled thru AccuRev support of their software. It seems like there would be a performance impact of issuing the accurev info command before every interaction with accurev. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-20903) Export Current Credentials as Environment Variables
Walter Kacynski commented on JENKINS-20903 Export Current Credentials as Environment Variables I guess that this problem is solved with the Credentials Binding Plugin https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Binding+Plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-24117) Support for proper shared clients/workspaces
Rob Petti
commented on JENKINS-24117
Support for proper shared clients/workspaces
Why can't you run things concurrent? Isn't that exactly what you are trying to accomplish?
When a job runs, and it's workspace is already in use, it creates a new one automatically and appends @# to it. There's no need to mess around with ${EXECUTOR_NUMBER}...
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-24118) Support for P4 TICKETS
Rob Petti closed JENKINS-24118 as Not A Defect Support for P4 TICKETS Change By: Rob Petti (06/Aug/14 3:00 PM) Status: Open Closed Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [selenium] (JENKINS-24129) Unexpected error in launching a slave. This is probably a bug in Jenkins.
Daniel Beck updated JENKINS-24129 Unexpected error in launching a slave. This is probably a bug in Jenkins. Given the NPE location it seems safe to assume an issue with the Selenium plugin. Change By: Daniel Beck (06/Aug/14 3:11 PM) Affects Version/s: current Component/s: ssh-slaves Component/s: python This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-24117) Support for proper shared clients/workspaces
Morne Joubert commented on JENKINS-24117 Support for proper shared clients/workspaces The whole idea is to 1) save space and 2) save time I have 50 jobs all using the same stream. Each time a job is running on a new executor it does a full sync (e.g. 10minutes vs 10s if an incremental sync could be done) and a new workspace is created. So for a slave of 16 executors: i will have 16x50 copies of the same source code. Now i want to run the same jobs on a second stream or 3 third stream or have 200 jobs. It just doesn't scale unless you have a massive amount of disk space and don't mind the sync time or P4 server overhead of managing all the have lists. So I have a working Jenkins system and i understand how all the bits work. I can just see that in 3 months we are going to run out of disk space. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-20903) Export Current Credentials as Environment Variables
Daniel Beck resolved JENKINS-20903 as Fixed Export Current Credentials as Environment Variables Reporter considers issue fixed by plugin. Change By: Daniel Beck (06/Aug/14 3:09 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-20966) SSH CLI -s option does not report Started jobname #58 until job finishes
SCM/JIRA link daemon resolved JENKINS-20966 as Fixed SSH CLI -s option does not report Started jobname #58 until job finishes Change By: SCM/JIRA link daemon (06/Aug/14 2:40 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-23882) Long build startup
Paul Allen commented on JENKINS-23882 Long build startup I have reduced the number of connections to Perforce when starting up (Unicode checks and extra login checks). This should speed up build start time. There are additional limits on changes and files when populating the build history. Target release 1.0.10 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial] (JENKINS-24136) Add support for build/release tagging with bookmarks
Jesse Glick commented on JENKINS-24136 Add support for build/release tagging with bookmarks Would be useful. Distinct from JENKINS-10558 which is about checking out a bookmark. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix] (JENKINS-23702) Matrix jobs consuming executors after upgrading to 1.570
Oleg Nenashev commented on JENKINS-23702 Matrix jobs consuming executors after upgrading to 1.570 The issue could be related to https://github.com/jenkinsci/throttle-concurrent-builds-plugin/pull/22 (no JIRA issue) Do you use throttle-concurrent-builds-plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [global-build-stats] (JENKINS-23836) NumberFormatException when clicking search button on Global Build Search
Oleg Nenashev updated JENKINS-23836 NumberFormatException when clicking search button on Global Build Search Change By: Oleg Nenashev (06/Aug/14 3:22 PM) Component/s: global-build-stats Component/s: plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial] (JENKINS-10558) Jenkins mercurial plugin - add support for bookmarks
Jesse Glick commented on JENKINS-10558 Jenkins mercurial plugin - add support for bookmarks Need to add MercurialSCM.RevisionType.BOOKMARK and then review test all operations (clone, update, poll, changelog) to make sure they work smoothly with bookmarks instead of branches, enabling the bookmark plugin if this is not already the default in Mercurial; and, as @igorkostenko noted, determine whether bookmarks are supportable with caching, and if not at least prevent the user from configuring a job with both bookmarks and caching. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23916) Adding a plugin to a build job which contains file upload button restricts user to rename the build job
Oleg Nenashev updated JENKINS-23916 Adding a plugin to a build job which contains file upload button restricts user to rename the build job Reassigned the issue to the core. Change By: Oleg Nenashev (06/Aug/14 3:23 PM) Component/s: core Component/s: plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24005) Pin build at Perforce Label does not support variable expansion
Paul Allen commented on JENKINS-24005 Pin build at Perforce Label does not support variable expansion Added support for label expansion in target 1.0.10 release. Tested OK with parameterized builds (NOTE: SCM Polling will not necessarily have access to these parameters). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-auth] (JENKINS-24134) Make environment variables available for Matrix Authorization Strategy Plugin
Jesse Glick resolved JENKINS-24134 as Not A Defect Make environment variables available for Matrix Authorization Strategy Plugin Does not make sense as written. If a job is being generated by some tool, then that tool should include any job-specific permissions in the config.xml, such as granting build permission to the user who initiated the generation. The matrix-auth plugin need not be modified. Change By: Jesse Glick (06/Aug/14 3:26 PM) Status: Open Resolved Assignee: JesseGlick Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [accurev] (JENKINS-10209) AccuRev plugin should work around accurev's spontaneous logout behaviour
pjdarton commented on JENKINS-10209 AccuRev plugin should work around accurevs spontaneous logout behaviour I guess your experience of "AccuRev support of their software" differs from my own. My opinions on this subject are not repeatable in polite company. We logged bugs; we showed proof. Then we gave up waiting and I made changes to the Jenkins-accurev plugin until it worked well enough that we weren't getting random builds failures several times a day. I'm not suggesting that one should re-issue the "accurev info" command before every command. As you rightly point out, the performance hit would be quite awful, and it wouldn't fix the problem either (as the login can expire spontaneously without warning, e.g. after the accurev info command has run and declared that you're logged in - once upon a time, I had Wireshark/ProcessMonitor/Console logs demonstrating this). What I am suggesting is that the code should detect when an accurev command fails and then, instead of just blindly declaring the entire build have failed (as it does now), it should examine the output of the command to see if it was an authentication problem, and if it was an authentication problem then it should re-run the "login if necessary" logic before re-retrying the command. I had hoped that my final paragraph of the original bug report had made this clear. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-20966) SSH CLI -s option does not report Started jobname #58 until job finishes
dogfood commented on JENKINS-20966 SSH CLI -s option does not report Started jobname #58 until job finishes Integrated in jenkins_main_trunk #3582 FIXED JENKINS-20966 flush output so cli get the build number being started (Revision eeebfee5d895dc27b46a77d1651b3d9d06a6bccc) Result = SUCCESS Nicolas De Loof : eeebfee5d895dc27b46a77d1651b3d9d06a6bccc Files : core/src/main/java/hudson/cli/BuildCommand.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout
Timothee Besset commented on JENKINS-23146 StringIndexOutOfBoundsException on subversion checkout Sorry @Daniel I have only basic understanding of java build ecosystems. Am I am able to download the 2.3 subversion plugin from somewhere and just plop it into my 'latest' Jenkins installation (running 1.574 atm)? I was looking at https://jenkins.ci.cloudbees.com/job/plugins/job/subversion-plugin/, but it seems it's compiling all pull requests, and I'm not sure how to get just this one or to 'apply' it to my Jenkins installation. The compile for pull #85 has expired and is no longer available. Any pointers would be greatly appreciated This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [accurev] (JENKINS-10209) AccuRev plugin should work around accurev's spontaneous logout behaviour
Walter Kacynski reopened JENKINS-10209 AccuRev plugin should work around accurevs spontaneous logout behaviour Right, this makes better sense now. Care would need to be taken that a login retry loop isn't going to occur. Other recent updates have also introduced command output parsing errors and I would think that these two items can be addressed together as better error handling. Change By: Walter Kacynski (06/Aug/14 3:54 PM) Resolution: Fixed Status: Resolved Reopened Assignee: pjdarton ScottTatum This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-23882) Long build startup
dan tran commented on JENKINS-23882 Long build startup tested with latest dev branch. Looking good for me This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-auth] (JENKINS-24134) Make environment variables available for Matrix Authorization Strategy Plugin
Max Krause commented on JENKINS-24134 Make environment variables available for Matrix Authorization Strategy Plugin Thanks for the tip! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-auth] (JENKINS-24134) Make environment variables available for Matrix Authorization Strategy Plugin
Max Krause closed JENKINS-24134 as Not A Defect Make environment variables available for Matrix Authorization Strategy Plugin Change By: Max Krause (06/Aug/14 4:01 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24138) Archived file names can change when moved from slave to master
Chris Rees commented on JENKINS-24138 Archived file names can change when moved from slave to master We patched the 1.8.3 ant with the fixes from 1.9.0 and dropped it into the Jenkins war and confirmed that Ant 1.9.0 would solve the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24138) Archived file names can change when moved from slave to master
Daniel Beck commented on JENKINS-24138 Archived file names can change when moved from slave to master Would probably be best if you could post the fix as a pull request on Github. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [selenium] (JENKINS-24129) Unexpected error in launching a slave. This is probably a bug in Jenkins.
Neal Storey commented on JENKINS-24129 Unexpected error in launching a slave. This is probably a bug in Jenkins. Disabling the Selenium Plugin did in fact bring the node back online. I attempted and uninstall but for whatever reason, it didn't uninstall. Re-enabling it caused the node to go offline again. I'm going to attempt a downgrade from 2.4.1 to 2.3 to see if I can at least get this operational again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24138) Archived file names can change when moved from slave to master
Chris Rees commented on JENKINS-24138 Archived file names can change when moved from slave to master I'll see what I can do. The fix was to change some of the Ant 1.8.3 behavior to match that of 1.9.0, which means Jenkins would either need to keep a modified copy of the file in source or update dependencies. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
David Tanner commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception This doesn't appear to be an issue with ghprb. Is there any more to the stack trace? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
