date:20140829















































Vincent Massol
 created  JENKINS-24506


NPE when sending an email in post build















Issue Type:


Bug



Affects Versions:


current



Assignee:


Alex Earl



Components:


email-ext



Created:


29/Aug/14 10:23 AM



Description:


Since we upgraded to Jenkins 1.577 (we also upgraded the Email Ext plugin to the latest 2.38.2), we now have NPE when our jobs fail and an email is trying to be sent:


The label "_xwiki_bin_get_Blog_GlobalBlogRss" caused the build to fail
Build step 'Publish Performance test result report' changed build result to FAILURE
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
ERROR: Could not send email as a part of the post-build publishers.
java.lang.NullPointerException
	at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:515)
	at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:290)
	at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:281)
	at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:233)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.cleanUp(MavenModuleSetBuild.java:1064)
	at hudson.model.Run.execute(Run.java:1786)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
	at hudson.model.ResourceController.execute(ResourceController.java:89)
	at hudson.model.Executor.run(Executor.java:240)
Finished: FAILURE



I check the code and the line 515 of ExtendedEmailPublisher.java:


for (RecipientProvider provider : context.getTrigger().getEmail().getRecipientProviders()) {



So this means either:

	context is null
	getTrigger() returns null
	getEmail() returns null



Any idea?

Thanks




Environment:


version 2.38.2




Project:


Jenkins



Priority:


Major



Reporter:


Vincent Massol

























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] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification

2014-08-29 Thread martin.h.schroe...@intel.com (JIRA)

Martin Schröder
commented on JENKINS-24445

Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification

Hi Rin.

I would consider it a critical issue, if

a feature that is linked-to from the main page's side-panel,
and activated by default for most users,
is breaking the fundamental assumption, that the Gerrit Trigger will only update the review

once all tests submitted for a given patch-sets have passed.

I am also not sure, if your assumptions about how many builds should be scheduled for events are entirely valid.
After all, the Gerrit Trigger plugin has another way of retriggering all builds belonging to a given patch-set:

Navigate to any build started by the patch-set in question, once it has finished.
You will see, in the side-panel of that build, a "Retrigger All" button.

This button does from the user perspective the same thing as the "manual trigger" and it works absolutely correctly because it can only be run, if all builds on that patch-set have finished.
That's the only reason it works. The manual trigger works, too, if you also wait until all builds for patch-set have finished.
Both features only break if you let them start concurrently with running tests.

But the problem is, that the manual trigger allows you to do that while other builds for the same patch-set are running. Since it does not check for this, it must work correctly even when builds are still running.
Otherwise, this feature is a direct way to break the entire purpose of the plugin.

And the nastiest thing: It breaks it without feedback. Nothing indicates that this behaviour breaks stuff. There isn't even an easy way to ensure that you can use that feature safely, as it not easy to find out which patch-sets are currently under test.

[JIRA] [core] (JENKINS-24500) IOexception when i saveproject setting.















































Daniel Beck
 commented on  JENKINS-24500


IOexception when i saveproject setting.















So far, nothing indicates this is actually a bug in Jenkins. Please make sure that the file is not locked by some other process (anti virus or search indexer come to mind). Use Process Explorer or similar tools to find out which processes access that file.



























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] [ownership] (JENKINS-24475) Managing ownership not possible















































Oleg Nenashev
 commented on  JENKINS-24475


Managing ownership not possible
















I tried with a clean jenkins instance (LTS 1.565.1), installing ownership plugin only; configured ownership to pin current user to created job; configured global security: all access to authenticated user, user self registration enabled; then registered myself, created a job. See myself as primary owner of the job. Taking the described action leads to the same error.

I cannot reproduce it on both ownership-0.4 and the current master version (I use the clean installation as well).
Are you sure that the page's JENKINS_URL does not change during your actions (e.g. from http://* to https://*)?



























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-24506) NPE when sending an email in post build















































Daniel Beck
 commented on  JENKINS-24506


NPE when sending an email in post build















Would be interesting to know which versions you were upgrading from.

Make sure the job configuration is valid (e.g. open it and save).



























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] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification















































Daniel Beck
 commented on  JENKINS-24445


Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification















"Critical" is used to indicate issues resulting in crashes, loss of data, severe memory leaks.



























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-24453) Jenkins server got blue screen to death















































Oleg Nenashev
 commented on  JENKINS-24453


Jenkins server got blue screen to death















@sharon

 Does that mean the latest 1.556.1 still has this issue?

Most probably, the answer is yes.
BTW, I cannot find any similar issues in Jenkins JIRA, hence I suppose that the issue does not appear on every Windows installation. 
Probably, it is somehow related to your system configurations or jobs running on the master node (they have Administrator privileges as well)

 Is it OK if I remove winp.x64.35A3F35D2ED629A6CEC5B41DD1D280C3.dll from the WEB-INF/lib folder?

No. You'll just corrupt the Jenkins installation with the unpredictable further behavior



























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-24506) NPE when sending an email in post build















































Vincent Massol
 commented on  JENKINS-24506


NPE when sending an email in post build















Note that I've just resaved the config for http://ci.xwiki.org/job/xwiki-enterprise-test-jmeter will let you know if it changes anything



























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-24462) Running a batch command failure
















































Oleg Nenashev
 resolved  JENKINS-24462 as Not A Defect


Running a batch command failure
















Jenkins has no wrappers for the automation of interactive operations.
You can use third-party apps for such purpose (just google it)





Change By:


Oleg Nenashev
(29/Aug/14 11:16 AM)




Status:


Reopened
Resolved





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] [email-ext] (JENKINS-24506) NPE when sending an email in post build















































Vincent Massol
 commented on  JENKINS-24506


NPE when sending an email in post build
















Would be interesting to know which versions you were upgrading from.

Yeah I know... Is there any way for me to find this out, seen that I had first upgraded to 2.38.1?

Note that it happened for this build which was in error (not a failure):
http://ci.xwiki.org/job/xwiki-enterprise-test-jmeter/187/console

We're still trying to find out if a failure would cause this problem too.

FYI this is what we were getting with 2.38.1: http://ci.xwiki.org/job/xwiki-platform_Sonar/232/console Apparently it was solved in 2.38.2 but the new problem (NPE) appeared...



























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] [copyartifact] (JENKINS-24084) Slave file leak build is interrupted during Copy Artifacts build step















































Oleg Nenashev
 updated  JENKINS-24084


Slave file leak build is interrupted during Copy Artifacts build step
















Change By:


Oleg Nenashev
(29/Aug/14 11:19 AM)




Labels:


remoting



























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-16737) java.lang.RuntimeException: No author in changeset null

2014-08-29 Thread abergme...@gmx.net (JIRA)















































Andreas Bergmeier
 commented on  JENKINS-16737


java.lang.RuntimeException: No author in changeset null















Same problem here. Kind of surprised that this has a Major prio since more than a year. Is there any way to analyze this or help otherwise?



























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] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb

2014-08-29 Thread tobias1...@gmail.com (JIRA)















































Tobias Schumacher
 commented on  JENKINS-11952


Emulator occasionally hangs indefinitely on startup, unable to connect adb















I have added a "good" log now. https://github.com/ITobiI/Android-Problem-Jenkins/blob/master/successful_build_log
I didn't find the passage you mentioned in the "good" log.



























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-16737) java.lang.RuntimeException: No author in changeset null

2014-08-29 Thread vincent.nougu...@astrium.eads.net (JIRA)















































Mark Waite
 commented on  JENKINS-16737


java.lang.RuntimeException: No author in changeset null















I think the priority is wrong.  The work around of wiping the workspace is relatively straightforward and has resolved the issue in all the cases where I've encountered it.  I've never had to take the second work around of removing the changelog.xml file.  Updating the slave.jar file did not seem to alter the seemingly random nature of the problem.

I've considered that it might be better for users if the getAuthorName() method were modified to never throw an exception, but always return something.  If the author name cannot be determined, then return something like "Unknown Author unkn...@bad.example.com".

Would that be enough better than the current state to be worth the effort to make the change?



























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] [ircbot] (JENKINS-24507) Publisher hudson.plugins.ircbot.IrcPublisher aborts due to exception when reporting on tests is enabled

2014-08-29 Thread bcooks...@kde.org (JIRA)















































Ben Cooksley
 created  JENKINS-24507


Publisher hudson.plugins.ircbot.IrcPublisher aborts due to exception when reporting on tests is enabled















Issue Type:


Bug



Affects Versions:


current



Assignee:


kutzi



Components:


ircbot



Created:


29/Aug/14 11:59 AM



Description:


Currently a number of our builds are being forced to fail by the IRC Notification component due to the following stacktrace:

ERROR: Publisher hudson.plugins.ircbot.IrcPublisher aborted due to exception
java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction;
	at hudson.plugins.im.build_notify.PrintFailingTestsBuildToChatNotifier.getFailedTestsReport(PrintFailingTestsBuildToChatNotifier.java:68)
	at hudson.plugins.im.build_notify.PrintFailingTestsBuildToChatNotifier.buildCompletionMessage(PrintFailingTestsBuildToChatNotifier.java:37)
	at hudson.plugins.im.IMPublisher.notifyChatsOnBuildEnd(IMPublisher.java:577)
	at hudson.plugins.im.IMPublisher.notifyOnBuildEnd(IMPublisher.java:304)
	at hudson.plugins.im.IMPublisher.perform(IMPublisher.java:291)
	at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)
	at hudson.model.Run.execute(Run.java:1765)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:89)
	at hudson.model.Executor.run(Executor.java:240)

Switching the Channel Notification Message to anything which does not mention "failed tests" will resolve the issue. It should be noted that this is only a problem if "failed tests" is selected as part of the Channel Notification Message and the build has tests which then fail.




Environment:


Jenkins 1.577




Project:


Jenkins



Priority:


Blocker



Reporter:


Ben Cooksley

























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] [clearcase] (JENKINS-24508) Cannot use parameters in load rules definition of a template project

Vincent Nouguier
created JENKINS-24508

Cannot use parameters in load rules definition of a template project

Issue Type:

Improvement

Affects Versions:

current

Assignee:

Vincent Latombe

Components:

clearcase

Created:

29/Aug/14 12:06 PM

Description:

I would like to define a "load rules" section with a parameter in a template project.
The parameter value would be defined in another 'concrete' job refering the template project scm configuration.

I tried the following:

I have a job named "my-template"
It is a parameterized build, defining parameter named "paramter1".
It defines a scm configuration whose load rules is :
/vob/myvob/${paramter1}

I have a job named "my-instance-0"
It defines "parameter1" value in section "Inject environment variables to the build process"
It defines the use of SCM from another project : my-template

When I look at "Base Clearcase Polling log", I see the parameter is not evaluated.

In EnvInject known limitations, i found in 'known limitations' section:
Only previous environment variables are available for polling
Some plugins provide polling mechanisms (such as SCM plugins, XTrigger plugins, ...) and you want to use injected environment variables in form fields of these plugins. Unfortunately, injected environment variables are processed only at build time therefore after the build is scheduled. Therefore, we can't access environment variables configured within the job. However, previous injected environment variables (from the previous build) are retrievable (implemented for example in the XTtrigger plugins). For the otehr plugins, authors are free to add the envinject-lib library dependency in their plugins in order to provide the ability to use environment variables given the EnvInject plugin.

Is there another to reach my needs ?
Is-it possible to take my needs into account in the next releases of clearcase plugin ?

Thanks

Project:

Jenkins

Priority:

Major

Reporter:

Vincent Nouguier

[JIRA] [git] (JENKINS-16737) java.lang.RuntimeException: No author in changeset null

2014-08-29 Thread sankar.bhe...@gmail.com (JIRA)















































sankar bheema
 commented on  JENKINS-16737


java.lang.RuntimeException: No author in changeset null















Hi Mark,

Wiping workspace is just temporary fix, again and again facing this issue from longtime, used option "commit author in changelog" also not fixed issue.

Regards,
Sankar Bheema.



























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] [ownership] (JENKINS-24475) Managing ownership not possible

2014-08-29 Thread stephan.kr...@ecg-leipzig.de (JIRA)















































Stephan Krull
 updated  JENKINS-24475


Managing ownership not possible
















Change By:


Stephan Krull
(29/Aug/14 12:17 PM)




Attachment:


installed_plugins.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] [ownership] (JENKINS-24475) Managing ownership not possible

2014-08-29 Thread stephan.kr...@ecg-leipzig.de (JIRA)















































Stephan Krull
 commented on  JENKINS-24475


Managing ownership not possible















No change in JENKINS_URL.

I tested with ownership-0.3 and get the same error. Responsibility for that error seems to be another component.

Find attached the list of active plugins in my fresh Jenkins LTS 1.565.1 instance. Could you please once again try to reproduce the error? Thank you!



























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-16737) java.lang.RuntimeException: No author in changeset null















































Mark Waite
 commented on  JENKINS-16737


java.lang.RuntimeException: No author in changeset null















I agree that wiping the workspace is just a temporary fix.  Unfortunately no one (including me) has been able to provide a set of steps which will consistently show the problem.  Without a set of steps to consistently show the problem, I have no reasonable way to decide if the bug is fixed.

My "thought experiment" to prevent a more serious problem (fail the build) when a minor problem happens (cannot compute the author of one of the changes) was to return an author that is wrong (like "Unknown Author unkn...@bad.example.com" rather than throwing a RuntimeException.  Is it better to fail the build with a RuntimeException when the author of a change cannot be computed, or is it better to return an author that is wrong but does not fail the build?

Is an accurate author for each change more important than a passing build?



























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] [ircbot] (JENKINS-24507) Publisher hudson.plugins.ircbot.IrcPublisher aborts due to exception when reporting on tests is enabled

2014-08-29 Thread nickbr...@gmail.com (JIRA)















































Nicholas Brown
 commented on  JENKINS-24507


Publisher hudson.plugins.ircbot.IrcPublisher aborts due to exception when reporting on tests is enabled















Perhaps related to JENKINS-24413 ?



























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] [ircbot] (JENKINS-24507) Publisher hudson.plugins.ircbot.IrcPublisher aborts due to exception when reporting on tests is enabled

2014-08-29 Thread bcooks...@kde.org (JIRA)















































Ben Cooksley
 commented on  JENKINS-24507


Publisher hudson.plugins.ircbot.IrcPublisher aborts due to exception when reporting on tests is enabled















Yes, the traces look identical. 



























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] [ownership] (JENKINS-24475) Managing ownership not possible

2014-08-29 Thread stephan.kr...@ecg-leipzig.de (JIRA)















































Stephan Krull
 commented on  JENKINS-24475


Managing ownership not possible















I can reproduce that same error on:

	Jenkins 1.577 fresh instance (running with "java -jar jenkins.war")
	without updating all the bundled plugins
	installing ownership-0.4
	configuring setup ownership when creating jobs
	configuring security and registering as a user
	creating a job and trying to manage ownership afterwards
	on firefox an ie



Any ideas what can lead to the redirect? 



























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] [instant-messaging] (JENKINS-24507) Publisher hudson.plugins.ircbot.IrcPublisher aborts due to exception when reporting on tests is enabled















































Daniel Beck
 updated  JENKINS-24507


Publisher hudson.plugins.ircbot.IrcPublisher aborts due to exception when reporting on tests is enabled
















Not sure which plugin (or both) are affected, adding IM component.





Change By:


Daniel Beck
(29/Aug/14 12:53 PM)




Component/s:


instant-messaging



























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-24509) Add token for EditType in CHANGES pathFormat















































Daniel Beck
 created  JENKINS-24509


Add token for EditType in CHANGES pathFormat















Issue Type:


New Feature



Assignee:


Alex Earl



Components:


email-ext



Created:


29/Aug/14 12:59 PM



Description:


There is currently no way to show the hudson.scm.EditType for a given path in email notifications. It would be great if this could be added to pathFormat, e.g. as initial letters for each change type (ADD = A, EDIT = E, DELETE = D).




Project:


Jenkins



Priority:


Major



Reporter:


Daniel Beck

























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-24509) Add token for EditType in CHANGES pathFormat















































Alex Earl
 commented on  JENKINS-24509


Add token for EditType in CHANGES pathFormat















Actually this does exist, in the path format the 'a' format token will show the name of the edit type and the 'd' format option will show the description.



























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-24506) NPE when sending an email in post build
















































Vincent Massol
 resolved  JENKINS-24506 as Cannot Reproduce


NPE when sending an email in post build
















Change By:


Vincent Massol
(29/Aug/14 1:07 PM)




Status:


Open
Resolved





Assignee:


AlexEarl
VincentMassol





Resolution:


CannotReproduce



























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-24506) NPE when sending an email in post build















































Vincent Massol
 commented on  JENKINS-24506


NPE when sending an email in post build















It was much better after I resaved the job's configuration, see http://ci.xwiki.org/job/xwiki-enterprise-test-jmeter/188/console

Now I get:


The label "_xwiki_bin_view_Blog_CategoriesPanel" caused the build to fail
Build step 'Publish Performance test result report' changed build result to FAILURE
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
An attempt to send an e-mail to empty list of recipients, ignored.
Finished: FAILURE



And this is normal. I didn't notice it at first but apparently we didn't have any recipient selected when the job fails!

Thanks again, closing



























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-24506) NPE when sending an email in post build















































Alex Earl
 commented on  JENKINS-24506


NPE when sending an email in post build















If there are no recipients it shouldn't error, I'll take a look.



























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-24506) NPE when sending an email in post build















































Alex Earl
 reopened  JENKINS-24506


NPE when sending an email in post build
















Change By:


Alex Earl
(29/Aug/14 1:09 PM)




Resolution:


CannotReproduce





Status:


Resolved
Reopened





Assignee:


VincentMassol
AlexEarl



























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-24509) Add token for EditType in CHANGES pathFormat
















































Daniel Beck
 resolved  JENKINS-24509 as Not A Defect


Add token for EditType in CHANGES pathFormat
















My apologies, I didn't realize I was still on 2.37.2.2.





Change By:


Daniel Beck
(29/Aug/14 1:13 PM)




Status:


Open
Resolved





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] [pretested-integration] (JENKINS-24284) In the commit message - don't write origin (our case 11769)
















































Andrius Ordojan
 resolved  JENKINS-24284 as Fixed


In the commit message - dont write origin (our case 11769)
















Change By:


Andrius Ordojan
(29/Aug/14 1:23 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] [pretested-integration] (JENKINS-24286) Plugin tries to delete origin/master (our case 11770)
















































Andrius Ordojan
 resolved  JENKINS-24286 as Fixed


Plugin tries to delete origin/master (our case 11770)
















Change By:


Andrius Ordojan
(29/Aug/14 1:24 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] [pretested-integration] (JENKINS-24285) Improve commit message (our case 11772)
















































Andrius Ordojan
 resolved  JENKINS-24285 as Fixed


Improve commit message (our case 11772)
















Change By:


Andrius Ordojan
(29/Aug/14 1:25 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] [pretested-integration] (JENKINS-24443) Use original commit object for author and commit message info (our case 11862)
















































Andrius Ordojan
 resolved  JENKINS-24443 as Fixed


Use original commit object for author and commit message info (our case 11862)
















Change By:


Andrius Ordojan
(29/Aug/14 1:28 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.

Re:

2014-08-29 Thread Stuart, Lisa

Reply for details, Mr. Tom Crist retired CEO  winner of $40m Dollar in Calgary 
Lotto made donation to you.

-- 
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] [job-dsl-plugin] (JENKINS-24510) AlwaysRun and NeverRun conditions are not supported by step.condition.SimpleCondition

2014-08-29 Thread roy...@gmail.com (JIRA)















































Roy Whytock
 created  JENKINS-24510


AlwaysRun and NeverRun conditions are not supported by step.condition.SimpleCondition















Issue Type:


Bug



Affects Versions:


current



Assignee:


Daniel Spilker



Components:


job-dsl-plugin



Created:


29/Aug/14 1:42 PM



Description:


The job-dsl run-condition-plugin support is incomplete as AlwaysRun and NeverRun are not supported by SimpleCondition. At present javaposse.jobdsl.dsl.helpers.step.condition.SimpleCondition assumes that condition classes end in Condition. However the AlwaysRun and NeverRun conditions do not require the Condition suffix.

Existing code
String getConditionClass() {
   "org.jenkins_ci.plugins.run_condition.${subPackage}.${name}Condition"
}

One possible solution
String getConditionClass() {
if (name.endsWith("Run")) {
return "org.jenkins_ci.plugins.run_condition.${subPackage}.${name}"
}
else {
return "org.jenkins_ci.plugins.run_condition.${subPackage}.${name}Condition"
}
}







Project:


Jenkins



Labels:


plugin




Priority:


Minor



Reporter:


Roy Whytock

























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-24506) NPE when sending an email in post build















































Daniel Beck
 commented on  JENKINS-24506


NPE when sending an email in post build















Probably a config migration issue. Vincent, do you use Job Config History or have a backup of the job configuration from before the update of email-ext?



























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-24506) NPE when sending an email in post build















































Alex Earl
 commented on  JENKINS-24506


NPE when sending an email in post build















Agreed, I need to check the upgrade path if there are no recipients for a given trigger and make sure that everything is correct.



























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-24506) NPE when sending an email in post build















































Vincent Massol
 commented on  JENKINS-24506


NPE when sending an email in post build















Sorry I don't have a backup of the job configuration...

Yes since resaving the job config worked, I believe the issue is in the upgrade path.



























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.

TRANSFORMANDO

2014-08-29 Thread Ruan Robson

BOM DIA!!!com o crescimento dos serviços online de compra e venda a
REALEMAIL esta recrutando pessoas pra trabalha via internet em casa
enviando e respondendo email é um trabalho simples porem muito sério,é pago
por comissão e chega a render 200 a 500 reais por semana é uma boa pedida
pra quem quer aumenta sua renda; para mas informação entre em contato
conosco.*http://www.realemail.onlinerenda.com.br/id:21808
http://www.realemail.onlinerenda.com.br/id:21808.*

Agradeço a atenção!
CAMILA SILVA E SILVA/RR

-- 
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-client] (JENKINS-21369) Git client fails to remove files/directories with git clean -fdx

2014-08-29 Thread stefan.kaltenber...@fabasoft.com (JIRA)















































Thomas COAN
 reopened  JENKINS-21369


Git client fails to remove files/directories with git clean -fdx
















Hi,
I face same issue :
It was working really until yesterday on a specific job (no changes on jenkins configuration for several weeks)

remark :
Other jobs are still working for the moment (with the same command run on their own git repo).


=
Error with StackTrace
=
Manually triggered by user anonymous for Gerrit: https://MY_GIT:8080/607665
Building in workspace http://MY_JENKINS:8080/jenkins/job/AR_VA_GerritVoter/ws/
  git.exe rev-parse --is-inside-work-tree
Fetching changes from the remote Git repository
  git.exe config remote.origin.url ssh://MY_GIT:29418/sandbox/MY.git
Fetching upstream changes from ssh://MY_GIT:29418/sandbox/MY.git
  git.exe --version
  git.exe fetch --tags --progress ssh://MY_GIT:29418/sandbox/MY.git	 refs/changes/65/607665/1
  git.exe rev-parse "c68be008cc694ffc7fa87e28baaf86245b696c1a^{commit}"
Checking out Revision c68be008cc694ffc7fa87e28baaf86245b696c1a (master)
  git.exe config core.sparsecheckout
  git.exe checkout -f c68be008cc694ffc7fa87e28baaf86245b696c1a
  git.exe rev-parse "FETCH_HEAD^{commit}"
  git.exe rev-list 445b38d8c3bbf8d5ef30f811b2c148fb356308ce
  git.exe tag -a -f -m Jenkins Build #359 jenkins-AR_VA_GerritVoter-359
Cleaning workspace
  git.exe rev-parse --verify HEAD
Resetting working tree
  git.exe reset --hard
  git.exe clean -fdx
FATAL: Command "git.exe clean -fdx" returned status code 1:
stdout: Removing com.sap.hilo.desktop.overlay/target/

stderr: warning: failed to remove com.sap.hilo.desktop.overlay/target/

hudson.plugins.git.GitException: Command "git.exe clean -fdx" returned status code 1:
stdout: Removing com.sap.hilo.desktop.overlay/target/

stderr: warning: failed to remove com.sap.hilo.desktop.overlay/target/

	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1406)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1382)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1378)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1092)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1102)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clean(CliGitAPIImpl.java:492)
	at hudson.plugins.git.GitAPI.clean(GitAPI.java:253)
	at hudson.plugins.git.extensions.impl.CleanCheckout.onCheckoutCompleted(CleanCheckout.java:28)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:908)
	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.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:234)


=
=== manual Check  ===
=
I have tryed to run the git command manually, and it seems to be the same problem  :
C:\.jenkins\jobs\AR_VA_GerritVoter\workspace\gitRepogit clean -fdx
Removing com.sap.hilo.desktop.overlay/target/
warning: failed to remove com.sap.hilo.desktop.overlay/target/

Note that /target folder is in .gitignore (for more than 1 month)





Change By:


Thomas COAN
(29/Aug/14 2:11 PM)




Resolution:


CannotReproduce





Status:


Resolved
Reopened



























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

[JIRA] [subversion] (JENKINS-23833) Subversion Plugin - can not checkout project due to OPTIONS request failed

2014-08-29 Thread mark_ffre...@hotmail.com (JIRA)















































Mark Ffrench
 commented on  JENKINS-23833


Subversion Plugin - can not checkout project due to OPTIONS request failed















I'm also getting this error. I have set up my Additional realm credentials as suggested in some similar tickets. I'm using my own svn credentials to authenticate jenkins, and interestingly it seems like only my changes are getting checked out without errors. The change log only reports my changes for the last few days, despite the fact that I can see plenty of other changes from other users using TortoiseSVN changelog.



























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] [gui] (JENKINS-10912) Browser/JS memory leak in dashboard















































Stefan Kaltenberger
 commented on  JENKINS-10912


Browser/JS memory leak in dashboard















In my case auto-refresh is disabled, so I guess it's not related (Jenkins ver. 1.576).



























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] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification

2014-08-29 Thread martin.h.schroe...@intel.com (JIRA)















































Martin Schröder
 updated  JENKINS-24445


Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
















Change By:


Martin Schröder
(29/Aug/14 2:40 PM)




Priority:


Critical
Major



























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] [radiatorview] (JENKINS-23924) New div layout breaks Radiator view

2014-08-29 Thread lorenzo.orsa...@gmail.com (JIRA)















































Lorenzo Orsatti
 commented on  JENKINS-23924


New div layout breaks Radiator view















It works also with 

div class="dashboard"
style="${dashStyle} overflow: hidden; left:
0px; top: 0px; position: fixed; height: 100%; width: 100%; z-index: 65535"




























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-client] (JENKINS-21369) Git client fails to remove files/directories with git clean -fdx















































Mark Waite
 commented on  JENKINS-21369


Git client fails to remove files/directories with git clean -fdx















Since your problem directory is the "target" directory, I suspect that one or more programs are holding that directory, or a file in that directory open.  Windows will not allow a file to be removed which is open by any process.  Windows will not allow a directory to be removed which includes any open file.

One simple technique to test the theory is to stop the slave agent and restart it.

Another simple technique is to restart the slave computer.

The Windows file removal poliicy is much more challenging than the Unix file removal policy, so another alternative is to prefer Unix based build machines instead of Windows machines.



























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] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification

2014-08-29 Thread martin.h.schroe...@intel.com (JIRA)















































Martin Schröder
 commented on  JENKINS-24445


Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification















Hi Daniel.

We originally set it to critical, because we consider corruption-of-data, by approving possibly unverified changes, to be pretty equivalent to loss-of-data.

I've bumped it down to "high" anyway, per your (and Rin's) recommendation.

We've simply disallowed the feature completely for all users, so it's not blocking us either.



























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] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification

2014-08-29 Thread martin.h.schroe...@intel.com (JIRA)













































 
Martin Schröder
 edited a comment on  JENKINS-24445


Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
















Hi Daniel.

We originally set it to critical, because we consider corruption-of-data, by approving possibly unverified changes, to be pretty equivalent to loss-of-data.

I've bumped it down to "major" anyway, per your (and Rin's) recommendation.

We've simply disallowed the feature completely for all users, so it's not blocking us either.



























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-client] (JENKINS-21369) Git client fails to remove files/directories with git clean -fdx















































Thomas COAN
 commented on  JENKINS-21369


Git client fails to remove files/directories with git clean -fdx















Thanks Mark,
I have tryed to run the job after a reboot = no old process holding the folder = same problem !
in batch mode (del /F/Q ...\target , it fails = no error, but no delete!)

However I have investigated on the commit that generates the problem, and I have found a new file that generates a path greater than 255 characters in my target folder.
Could it be the root cause ?

I will check with the dev if he can change it and keep you in touch

I cannot  switch on a unix machine (not owned by myself !)



























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-client] (JENKINS-21369) Git client fails to remove files/directories with git clean -fdx















































Daniel Beck
 commented on  JENKINS-21369


Git client fails to remove files/directories with git clean -fdx















Issue report needs to show that this is a problem with Jenkins. The Sysinternals tools (e.g. Process Explorer) could help determining which process is holding a file handle.



























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-client] (JENKINS-21369) Git client fails to remove files/directories with git clean -fdx















































Daniel Beck
 commented on  JENKINS-21369


Git client fails to remove files/directories with git clean -fdx















FWIW I've repeatedly had to remind my users to log out of the build server instead of just closing the RDC session  make sure there are no sessions with e.g. a cmd.exe in that directory open.



























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-client] (JENKINS-21369) Git client fails to remove files/directories with git clean -fdx















































Daniel Beck
 commented on  JENKINS-21369


Git client fails to remove files/directories with git clean -fdx















Sorry, didn't see the comment posted just before mine. It's likely that the long path is the problem in which case this is Not a Defect in Jenkins.

A few suggestions if you're right around ~260 chars and your developer is being stubborn:


	Use a short Jenkins (master/slave) root directory, e.g. D:\J
	Change the Workspace Root Directory on the master completely (Configure System; Advanced), e.g. D:\WS if building on the master
	Set the hudson.model.Slave.workspaceRoot system property to something shorter than workspace if building on a slave
	Set the hudson.matrix.MatrixConfiguration.useShortWorkspaceName system property to true for any Multi-configuration projects
	Configure a custom workspace in Advanced Project Options





























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-client] (JENKINS-21369) Git client fails to remove files/directories with git clean -fdx















































Thomas COAN
 commented on  JENKINS-21369


Git client fails to remove files/directories with git clean -fdx















I have done a test after a reboot of the machine on jenkins console (without RDC) = failed
In process explorer no process is handling the folder.


Ok problem comes from the length of windows path   255.
Problem is solved for us = should be a jenkins restriction



























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-client] (JENKINS-21369) Git client fails to remove files/directories with git clean -fdx













































 
Thomas COAN
 edited a comment on  JENKINS-21369


Git client fails to remove files/directories with git clean -fdx
















Ok problem comes from the length of windows path   255.
Problem is solved for us = should be a jenkins restriction

I will check your proposition but we have some restrictions as some jobs are generated by an automate (= to do in our side for the choice of folder names)



























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-client] (JENKINS-21369) Git client fails to remove files/directories with git clean -fdx













































 
Thomas COAN
 edited a comment on  JENKINS-21369


Git client fails to remove files/directories with git clean -fdx
















Ok problem comes from the length of windows path   255.
Problem is solved for us = should be a jenkins restriction

thanks Daniel,
I will check your proposition but we have some restrictions as some jobs are generated by an automate (= to do in our side for the choice of folder names)



























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-client] (JENKINS-21369) Git client fails to remove files/directories with git clean -fdx
















































Mark Waite
 closed  JENKINS-21369 as Fixed


Git client fails to remove files/directories with git clean -fdx
















Change By:


Mark Waite
(29/Aug/14 3:24 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] [git-client] (JENKINS-21369) Git client fails to remove files/directories with git clean -fdx

2014-08-29 Thread daniel.kuchelmeis...@elektrobit.com (JIRA)
















































Mark Waite
 resolved  JENKINS-21369 as Fixed


Git client fails to remove files/directories with git clean -fdx
















Change By:


Mark Waite
(29/Aug/14 3:24 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] [integrity-plugin] (JENKINS-14706) Integrity Plugin should create *.pj files, too

Daniel Kuchelmeister
reopened JENKINS-14706

Integrity Plugin should create *.pj files, too

Hey Cletus,

Sorry for bothering you with this one again, its just to have a final statement from you about maybe supplying or totally refusing 'si createsandbox' support.

Background is, in my company we have various tools that need a registered sandbox of the integrity project for e.g version information, that are used for releasenotes and the graphical integrity client is installed anyway.

I totally understand you with relying on the Integrity Java API since we have an own Integrity plugin implementation using the CLI tools provided by the IntegrityClient installation. I'm currently trying to make this implementation stable but it is suffering from instablilities by the client itself (we are bound to version 10.1x) and for some cases it looks nearly impossible to work arround bugs in the client (Out of memory/Stackoverflow errors) leaving the client irresponsible) imposed by the distributed design si/integrityg/IntegrityClient...

Because of these issues i'm having a hard time thinking about working arround these problems or switching to the Java API too. Easiest way would be to have a checkbox 'Create Sandbox' replacing the 'projectco' commands in your implementation by 'createsandbox'. Do you think of the changes as being complex? I do not have any experience with the Java API and first observation of your current sources didn't get me far.

i' willing to contribute for having a stable solution, some recommandations?

br
Daniel

Change By:

Daniel Kuchelmeister
(29/Aug/14 3:33 PM)

Resolution:

WontFix

Status:

Resolved
Reopened

[JIRA] [git] (JENKINS-23489) Failed to fetch from bitbucket private repository
















































Mark Waite
 closed  JENKINS-23489 as Fixed


Failed to fetch from bitbucket private repository
















Change By:


Mark Waite
(29/Aug/14 3:59 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] [git] (JENKINS-24086) Add GIT_SPARSE or similar environment variable
















































Mark Waite
 closed  JENKINS-24086 as Wont Fix


Add GIT_SPARSE or similar environment variable
















Change By:


Mark Waite
(29/Aug/14 3:58 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] [git] (JENKINS-23091) Git. Problem with encoding in the list changes
















































Mark Waite
 closed  JENKINS-23091 as Fixed


Git. Problem with encoding in the list changes
















Believed fixed in git plugin 2.2.4 and later





Change By:


Mark Waite
(29/Aug/14 3:59 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] [git] (JENKINS-22640) Notify commit can't find job by URI
















































Mark Waite
 closed  JENKINS-22640 as Not A Defect


Notify commit cant find job by URI
















Polling must be enabled since the notify commit message causes a poll.  If polling is not enabled, then the notify should not cause the job to poll.

I believe the rationale for the notify hook using a poll is described in the "polling must die" blog posting from Kohsuke





Change By:


Mark Waite
(29/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] [git] (JENKINS-22407) Git repository browser URL goes missing
















































Mark Waite
 closed  JENKINS-22407 as Fixed


Git repository browser URL goes missing
















Change By:


Mark Waite
(29/Aug/14 4:05 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] [git] (JENKINS-17700) Windows: Git clone fails on computer with multiple executors or slaves
















































Mark Waite
 closed  JENKINS-17700 as Not A Defect


Windows: Git clone fails on computer with multiple executors or slaves
















Change By:


Mark Waite
(29/Aug/14 4:07 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] [git] (JENKINS-22156) Git Plugin Json call key error for Jenkins job trigged by polling
















































Mark Waite
 closed  JENKINS-22156 as Not A Defect


Git Plugin Json call key error for Jenkins job trigged by polling
















Change By:


Mark Waite
(29/Aug/14 4:06 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] [git] (JENKINS-17894) Can't Clone Git repository over SSH 'Process leaked file descriptors'
















































Mark Waite
 closed  JENKINS-17894 as Not A Defect


Cant Clone Git repository over SSH Process leaked file descriptors
















Change By:


Mark Waite
(29/Aug/14 4:08 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] [git] (JENKINS-17710) Windows: Using Shallow Clone cause a git fatal error - pack has 1 unresolved delta (index-pack failed)
















































Mark Waite
 closed  JENKINS-17710 as Wont Fix


Windows: Using Shallow Clone cause a git fatal error - pack has 1 unresolved delta (index-pack failed)
















Change By:


Mark Waite
(29/Aug/14 4:08 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] [git] (JENKINS-18232) How do I enable slave logging?
















































Mark Waite
 closed  JENKINS-18232 as Not A Defect


How do I enable slave logging?
















Change By:


Mark Waite
(29/Aug/14 4:09 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] [git] (JENKINS-18328) GitLab repoisitory browser creates defective file link
















































Mark Waite
 closed  JENKINS-18328 as Fixed


GitLab repoisitory browser creates defective file link
















Change By:


Mark Waite
(29/Aug/14 4:09 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] [git] (JENKINS-18303) Cannot do checkout of a git repository in BitBucket in Jenkins
















































Mark Waite
 closed  JENKINS-18303 as Fixed


Cannot do checkout of a git repository in BitBucket in Jenkins
















Change By:


Mark Waite
(29/Aug/14 4:09 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] [git] (JENKINS-18343) Another O(n^2) algorithm creates 100% CPU usage
















































Mark Waite
 closed  JENKINS-18343 as Fixed


Another O(n^2) algorithm creates 100% CPU usage
















Change By:


Mark Waite
(29/Aug/14 4:10 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] [git] (JENKINS-17218) Environment variables broken in git 1.3 plug-in
















































Mark Waite
 closed  JENKINS-17218 as Wont Fix


Environment variables broken in git 1.3 plug-in
















Change By:


Mark Waite
(29/Aug/14 4:14 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] [git] (JENKINS-17198) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files
















































Mark Waite
 closed  JENKINS-17198 as Fixed


Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files
















Change By:


Mark Waite
(29/Aug/14 4:14 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] [git] (JENKINS-17164) Failed to record SCM polling for hudson.model.FreeStyleProject
















































Mark Waite
 closed  JENKINS-17164 as Fixed


Failed to record SCM polling for hudson.model.FreeStyleProject
















No further reports on this, and no indications that it is still an issue.





Change By:


Mark Waite
(29/Aug/14 4:16 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] [git] (JENKINS-17150) GIT_BRANCH should never have 'HEAD' value
















































Mark Waite
 closed  JENKINS-17150 as Fixed


GIT_BRANCH should never have HEAD value
















Change By:


Mark Waite
(29/Aug/14 4:16 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] [git] (JENKINS-17195) InvalidTagNameException with version 1.0.4 of git client
















































Mark Waite
 closed  JENKINS-17195 as Fixed


InvalidTagNameException with version 1.0.4 of git client
















Change By:


Mark Waite
(29/Aug/14 4:15 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] [git] (JENKINS-17055) Git 1.2: only one remote is actually added
















































Mark Waite
 closed  JENKINS-17055 as Fixed


Git 1.2: only one remote is actually added
















Change By:


Mark Waite
(29/Aug/14 4:18 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] [git] (JENKINS-17020) [Git plugin] Implement proper http authentication
















































Mark Waite
 closed  JENKINS-17020 as Fixed


[Git plugin] Implement proper http authentication
















Change By:


Mark Waite
(29/Aug/14 4:18 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] [git] (JENKINS-17013) Git plugin fails with NPE (Jenkins 1.502, 1.503)
















































Mark Waite
 closed  JENKINS-17013 as Fixed


Git plugin fails with NPE (Jenkins 1.502, 1.503)
















Change By:


Mark Waite
(29/Aug/14 4:19 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] [git] (JENKINS-16994) Solve bad naming in Git 'Installation directory' vs. 'Path to executable'
















































Mark Waite
 closed  JENKINS-16994 as Fixed


Solve bad naming in Git Installation directory vs. Path to executable
















Change By:


Mark Waite
(29/Aug/14 4:20 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] [git] (JENKINS-16684) Add GIT_URL to build environment