date:20140324















































Mark Waite
 commented on  JENKINS-22319


Updating Git plugin causes existing builds to immediately fail















Thanks for the report.  Can you upload the job definition of one of the failing 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] [subversion] (JENKINS-14155) Automatically select/build the latest svn tag (via List Subversion tags build params?)

2014-03-24 Thread bag...@rediffmail.com (JIRA)















































S B
 commented on  JENKINS-14155


Automatically select/build the latest svn tag (via List Subversion tags build params?)















Hi Guys,

Do we have this option enabled as to "select newest automatically" in List Subversion tags while polling in CI builds.



























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-22085) git plugin should allow perform clone with --single-branch parameter to speed up (requires git 1.7.10+)















































Mark Waite
 commented on  JENKINS-22085


git plugin should allow perform clone with --single-branch parameter to speed up (requires git 1.7.10+)















The "git clone" man page says that --single-branch is the default if "git clone --shallow" is used.  There is a "shallow" option in the git plugin.  Have you checked to see if using the shallow option already satisfies your need?

It may not meet your need because the plugin used git fetch and git init so that it can provide credentials support.



























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] [maven2] (JENKINS-9030) Disable Archiving for all Maven Jobs

2014-03-24 Thread docw...@gerf.org (JIRA)

Christian Höltje
commented on JENKINS-9030

Disable Archiving for all Maven Jobs

I use the Job DSL to create my jobs and I keep forgetting about the "Disable automatic artifact archiving" option (under "Build", then click "Advanced" to show it).

The help text in 1.532.1 reads:

If checked, Jenkins will not automatically archive all artifacts generated by this project. If you wish to archive the results of this build within Jenkins, you will need to use the "Archive the Artifacts" post-build action below.

I've had problems with running out of space multiple times on different servers (I've set up Jenkins for other groups in our business) because we use Nexus for managing artifacts.

If you google for this option, you'll see tons of emails, posts, etc. telling people to "Disable automatic artifact archiving".

I'm assuming there is an advantage to not checking this box, but I'm unsure what it is.

I have two possible suggestions:

Reverse the flag: [] Enable automatic maven artifact archiving

Alternatively, (assuming it provides something above and beyond mere "Archive Artifacts") move the option down to a "Post Build" step, next to archive artifacts so that it is obvious.

Another option is to move it into the Archive Artifacts plugin.

Ciao!

[JIRA] [core] (JENKINS-19544) OutOfMemory due to unbounded storage in OldDataMonitor

2014-03-24 Thread sagi.sinai-gla...@ericsson.com (JIRA)















































Sagi Sinai-Glazer
 commented on  JENKINS-19544


OutOfMemory due to unbounded storage in OldDataMonitor















Will this fix be back-ported to LTS versions?



























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-14155) Automatically select/build the latest svn tag (via List Subversion tags build params?)

2014-03-24 Thread pmora...@gmail.com (JIRA)















































Pedro Goncalves
 commented on  JENKINS-14155


Automatically select/build the latest svn tag (via List Subversion tags build params?)















Hi S B,
Sorry, I just made a fresh install from Jenkins, and I don't see this option there. Can you show us ?

kind regards,



























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-19976) Cannot load a class in depended plugin after install before restart















































Jesse Glick
 started work on  JENKINS-19976


Cannot load a class in depended plugin after install before restart
















Change By:


Jesse Glick
(24/Mar/14 1:56 PM)




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] [core] (JENKINS-19544) OutOfMemory due to unbounded storage in OldDataMonitor















































Jesse Glick
 commented on  JENKINS-19544


OutOfMemory due to unbounded storage in OldDataMonitor















@esinsag I can mark it as a candidate for consideration.



























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-19544) OutOfMemory due to unbounded storage in OldDataMonitor















































Jesse Glick
 updated  JENKINS-19544


OutOfMemory due to unbounded storage in OldDataMonitor
















Change By:


Jesse Glick
(24/Mar/14 2:02 PM)




Labels:


lts-candidate
memory-leakperformance



























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] [websphere-deployer] (JENKINS-21643) Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)

2014-03-24 Thread gregpeter...@gmail.com (JIRA)















































Greg Peters
 reopened  JENKINS-21643


Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)
















Reopening to evaluate





Change By:


Greg Peters
(24/Mar/14 2:27 PM)




Resolution:


WontFix





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 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] [websphere-deployer] (JENKINS-21643) Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)

2014-03-24 Thread khalil.reh...@aviva.com (JIRA)















































kal
 commented on  JENKINS-21643


Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)















Apologies guys, I am diverted to some other project work but will be coming back to this in next few days



























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] [jacoco] (JENKINS-22324) JacocoPublisher aborted due to java.util.zip.ZipException: invalid entry size

2014-03-24 Thread david_mil...@notesdev.ibm.com (JIRA)















































David Miller
 created  JENKINS-22324


JacocoPublisher aborted due to java.util.zip.ZipException: invalid entry size















Issue Type:


Bug



Assignee:


Ognjen Bubalo



Components:


jacoco



Created:


24/Mar/14 2:36 PM



Description:


We are getting intermittent occurrences of a Jacoco exception below. If we re-run the exact same Jenkins job, we won't get the error and the code coverage results are reported OK.

Archiving artifacts
Recording test results
JaCoCo plugin Collecting JaCoCo coverage data...
JaCoCo plugin src/sn.comm/lwp/comm.test/bvt/*.exec;jars_original;tmp_jacoco; locations are configured
JaCoCo plugin Number of found exec files: 1
JaCoCo plugin Saving matched execfiles:  http://jenkinspoc.swg.usma.ibm.com/jenkins/job/Communities_UT/ws/src/sn.comm/lwp/comm.test/bvt/jacoco.exec
JaCoCo plugin Saving matched class directories:  http://jenkinspoc.swg.usma.ibm.com/jenkins/job/Communities_UT/ws/jars_original
JaCoCo plugin Saving matched source directories:  http://jenkinspoc.swg.usma.ibm.com/jenkins/job/Communities_UT/ws/tmp_jacoco
JaCoCo plugin Loading inclusions files..
JaCoCo plugin inclusions: []
JaCoCo plugin exclusions: []
ERROR: Publisher hudson.plugins.jacoco.JacocoPublisher aborted due to exception
java.util.zip.ZipException: invalid entry size (expected 14808 but got 19284 bytes)
		 at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:387)
		 at java.util.zip.ZipInputStream.read(ZipInputStream.java:156)
		 at java.util.zip.ZipInputStream.closeEntry(ZipInputStream.java:100)
		 at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:78)
		 at org.jacoco.core.analysis.Analyzer.analyzeArchive(Analyzer.java:131)
		 at org.jacoco.core.analysis.Analyzer.analyzeAll(Analyzer.java:158)
		 at org.jacoco.core.analysis.Analyzer.analyzeAll(Analyzer.java:183)
		 at hudson.plugins.jacoco.ExecutionFileLoader.analyzeStructure(ExecutionFileLoader.java:131)
		 at hudson.plugins.jacoco.ExecutionFileLoader.loadBundleCoverage(ExecutionFileLoader.java:138)
		 at hudson.plugins.jacoco.JacocoReportDir.parse(JacocoReportDir.java:102)
		 at hudson.plugins.jacoco.JacocoBuildAction.loadRatios(JacocoBuildAction.java:278)
		 at hudson.plugins.jacoco.JacocoBuildAction.load(JacocoBuildAction.java:260)
		 at hudson.plugins.jacoco.JacocoPublisher.perform(JacocoPublisher.java:380)
		 at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
		 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
		 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776)
		 at hudson.model.Build$BuildExecution.post2(Build.java:183)
		 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:725)
		 at hudson.model.Run.execute(Run.java:1701)
		 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
		 at hudson.model.ResourceController.execute(ResourceController.java:88)
		 at hudson.model.Executor.run(Executor.java:231)




Environment:


Jenkins 1.5.5.3, Jacoco plug-in 1.0.14, GNU/Linux 2.6.18-371.4.1.el5 x86_64




Project:


Jenkins



Priority:


Major



Reporter:


David Miller

























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

[JIRA] [parameterized-trigger] (JENKINS-22229) Build from properties file fails if workspace does not exist

2014-03-24 Thread cmay...@cisco.com (JIRA)















































Caleb Mayeux
 commented on  JENKINS-9


Build from properties file fails if workspace does not exist















@ikeadam, yes, I'd like the plugin to support absolute or relative (to workspace) path, with support for token macros (variables). I'm not really asking for a new feature, as this support already exists. There's just a few lines of code that were introduced that skip the path resolution if the workspace was already deleted that I'd like to remove. I did a pull request for this here: https://github.com/jenkinsci/parameterized-trigger-plugin/pull/64



























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-17526) Broken CSS when reloading Jenkins after a time of inactivity

2014-03-24 Thread to...@lark-it.com (JIRA)















































Tommy McNeely
 commented on  JENKINS-17526


Broken CSS when reloading Jenkins after a time of inactivity















The commit mentioned only fixes Mac OSX, however I have also seen this issue on CentOS 6 (or probably any other Linux or Unix) with tmpwatch installed. I would strongly recommend defaulting to /var/run/jenkins or something similar, across all *nix like OS's. You can currently either edit /etc/default/jenkins to change the tmpdir (similar to the commit), or edit /etc/cron.daily/tmpwatch to exclude it as @akiko_pusu mentioned above.



























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] [repository] (JENKINS-15714) HTTP 500 Internal Exception accessing Maven Repository URL for specific builds















































SCM/JIRA link daemon
 commented on  JENKINS-15714


HTTP 500 Internal Exception accessing Maven Repository URL for specific builds















Code changed in jenkins
User: magnayn
Path:
 repository-hpi/src/main/java/com/nirima/jenkins/repo/project/ProjectBuildList.java
http://jenkins-ci.org/commit/maven-repository-plugin/83781d83b7876f73fba2eed5725a92b0ac38b8cb
Log:
  Merge pull request #11 from victorbr/master

Fixed JENKINS-15714





























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] [repository] (JENKINS-22302) StringIndexOutOfBoundsException: String index out of range: -35















































SCM/JIRA link daemon
 commented on  JENKINS-22302


StringIndexOutOfBoundsException: String index out of range: -35















Code changed in jenkins
User: magnayn
Path:
 pom.xml
 repository-hpi/pom.xml
 repository-hpi/src/main/java/com/nirima/jenkins/webdav/impl/methods/MethodBase.java
http://jenkins-ci.org/commit/maven-repository-plugin/693a455fa9edb6573c735363419c927efc4e32fe
Log:
  Merge pull request #20 from ndeloof/master

JENKINS-22302


Compare: https://github.com/jenkinsci/maven-repository-plugin/compare/745545f8a7aa...693a455fa9ed




























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] [repository] (JENKINS-22302) StringIndexOutOfBoundsException: String index out of range: -35
















































SCM/JIRA link daemon
 resolved  JENKINS-22302 as Fixed


StringIndexOutOfBoundsException: String index out of range: -35
















Change By:


SCM/JIRA link daemon
(24/Mar/14 2:49 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] [repository] (JENKINS-22302) StringIndexOutOfBoundsException: String index out of range: -35















































SCM/JIRA link daemon
 commented on  JENKINS-22302


StringIndexOutOfBoundsException: String index out of range: -35















Code changed in jenkins
User: Nicolas De Loof
Path:
 repository-hpi/src/main/java/com/nirima/jenkins/webdav/impl/methods/MethodBase.java
http://jenkins-ci.org/commit/maven-repository-plugin/1caee1ed94c9b8e4260c47740a9a1f9dce0733fd
Log:
  FIXED JENKINS-22302 consider servletPath when pathInfo is null





























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] [repository] (JENKINS-15714) HTTP 500 Internal Exception accessing Maven Repository URL for specific builds















































SCM/JIRA link daemon
 commented on  JENKINS-15714


HTTP 500 Internal Exception accessing Maven Repository URL for specific builds















Code changed in jenkins
User: Victor Bronstein
Path:
 repository-hpi/src/main/java/com/nirima/jenkins/repo/project/ProjectBuildList.java
http://jenkins-ci.org/commit/maven-repository-plugin/398b461aa24727c5f062b6bce133eb4cdbd3fbd4
Log:
  FIXED JENKINS-15714 HTTP 500 Internal Exception accessing Maven Repository URL for specific builds

The code attempted to modify a read-only view returned by Guava collections utilities. Modified it to use filtering instead.





























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-17526) Broken CSS when reloading Jenkins after a time of inactivity

2014-03-24 Thread to...@lark-it.com (JIRA)

Tommy McNeely
edited a comment on JENKINS-17526

Broken CSS when reloading Jenkins after a time of inactivity

The commit mentioned only fixes Mac OSX, however I have also seen this issue on CentOS 6 (or probably any other Linux or Unix) with tmpwatch installed. I would strongly recommend defaulting to /var/run/jenkins or something similar, across all nix like OS's. The current workaround is to either edit /etc/default/jenkins to change the tmpdir (similar to the commit), or edit /etc/cron.daily/tmpwatch to exclude it as @akiko_pusu mentioned above. As I don't think the Jenkins package should be futzing with the tmpwatch cron job, it makes the most sense, in my opinion, to default to a different tmpdir location. Note that this would also require the directory to be created with the proper permissions. The /var/run/jenkins directory could be created by the package, but it *should be checked and created if necessary during the init script because some OS's (Solaris) tend to mount /var/run on tmpfs.

[JIRA] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity

2014-03-24 Thread to...@lark-it.com (JIRA)

Tommy McNeely
edited a comment on JENKINS-17526

Broken CSS when reloading Jenkins after a time of inactivity

The commit mentioned only fixes Mac OSX, however I have also seen this issue on CentOS 6 (or probably any other Linux or Unix) with tmpwatch installed. I would strongly recommend defaulting to /var/run/jenkins or something similar, across all *nix like OS's. The current workaround is to either edit /etc/default/jenkins to change the tmpdir (similar to the commit), or edit /etc/cron.daily/tmpwatch to exclude it as @akiko_pusu mentioned above. As I don't think the Jenkins package should be futzing with the tmpwatch cron job, it makes the most sense, in my opinion, to default to a different tmpdir location. Note that this would also require the directory to be created with the proper permissions. The /var/run/jenkins directory could be created by the package, but it should be checked and created if necessary during the init script because some OS's (Solaris) tend to mount /var/run on tmpfs.

[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build

2014-03-24 Thread de...@ikedam.jp (JIRA)

ikedam
commented on JENKINS-22212

No e-mail sent after failed build triggered from another build

Sorry, that's my mistake.
It requires using fingerprints to have Jenkins recognize "upstream" and "downstream".

This would be done in following way (but not so simple...):

In upstream project, fingerprint the revision as following:

run following script with "Execute shell":

echo ${SVN_REVISION} revision.txt

Call "Record fingerprints of files to track usage" for "revision.txt"
Pass SVN_REVISION to downstream project as following with "Predefined Parameters" in "Trigger parameterized build on other projects"

UPSTREAM_SVN_REVISION=${SVN_REVISION}

As you use "Include/passthrough Upstream SVN Revisons", SVN_REVISION may be passed to downstream automatically. I cannot test as I don't use subversion in my environment.

Also in downstream project, fingerprint the revision as following:

run following script with "Execute shell":

echo ${UPSTREAM_SVN_REVISION} revision.txt

Call "Record fingerprints of files to track usage" for "revision.txt"

This should be called before calling Email-ext.

You can see fingerprints work correct in "See Fingerprints" of the build page.
And you can also test in Manage Jenkins Script Console:

hudson.model.AbstractBuild.upstreamCulprits

Returns true if hudson.upstreamCulprits is successfully configured.

Jenkins.instance.getItemByFullName("downstreamProjectName").lastBuild.getDependencyChanges(Jenkins.instance.getItemByFullName("downstreamProjectName").lastBuild.previousBuild)

Returns upstream build if successfully tracked using fingerprints

Jenkins.instance.getItemByFullName("downstreamProjectName").lastBuild.culprits

Returns upstream developers if upstreamCulprits (and fingerprints) work successfully.

[JIRA] [parameterized-remote-trigger] (JENKINS-22325) Parameterized Remote Trigger Plugin fails with 'FATAL: Invalid JSON String' after triggering the remote build

2014-03-24 Thread maik.sko...@gmail.com (JIRA)















































Maik Skorna
 created  JENKINS-22325


Parameterized Remote Trigger Plugin fails with FATAL: Invalid JSON String after triggering the remote build















Issue Type:


Bug



Affects Versions:


current



Assignee:


Maurice W.



Components:


parameterized-remote-trigger



Created:


24/Mar/14 3:17 PM



Description:


I've a local jenkins server and provided a remote jenkins server.

My local build is triggering the remote build, which is running and being built successfully, but the local job fails with the following exception:


Triggering this remote job: REMOTE_BUILD_JOB
Not checking if the remote job REMOTE_BUILD_JOB is building.
This job is build #[12] on the remote server.
Triggering remote job now.
FATAL: Invalid JSON String
net.sf.json.JSONException: Invalid JSON String
	at net.sf.json.JSONSerializer.toJSON(JSONSerializer.java:143)
	at net.sf.json.JSONSerializer.toJSON(JSONSerializer.java:103)
	at net.sf.json.JSONSerializer.toJSON(JSONSerializer.java:84)
	at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.sendHTTPCall(RemoteBuildConfiguration.java:698)
	at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.perform(RemoteBuildConfiguration.java:529)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:784)
	at hudson.model.Build$BuildExecution.build(Build.java:199)
	at hudson.model.Build$BuildExecution.doRun(Build.java:160)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:565)
	at hudson.model.Run.execute(Run.java:1670)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:231)


Any suggestions what could be wrong?




Environment:


Jenkins ver. 1.550

Parameterized Remote Trigger Plugin ver 2.1




Project:


Jenkins



Priority:


Major



Reporter:


Maik Skorna

























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] [build-pipeline] (JENKINS-20873) Run button does not work with Parametrized builds

2014-03-24 Thread dennis.schu...@codecentric.de (JIRA)















































Dennis Schulte
 commented on  JENKINS-20873


Run button does not work with Parametrized builds















How is the status for this bug? Will it be 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] [git] (JENKINS-22319) Updating Git plugin causes existing builds to immediately fail

2014-03-24 Thread jo...@alenius.se (JIRA)















































Johan Alenius
 commented on  JENKINS-22319


Updating Git plugin causes existing builds to immediately fail















I just upgraded the Git plugin from 2.0.1 to 2.0.4 and got the same error:
ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.

Do you specify remotes/origin/master as "Branches to build"? Changing it to just master seems to solve it, see JENKINS-20767. The git client plugin will prefix the branch with name or origin if name is left blank.



























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] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build

2014-03-24 Thread aik.b...@gmail.com (JIRA)















































Alexander Obuhovich
 commented on  JENKINS-22212


No e-mail sent after failed build triggered from another build















echo ${SVN_REVISION} revision.txt

I don't get it. I dump the SVN revision to "revision.txt" in both upstream and downstream projects, but why? Maybe a mistake?

Call "Record fingerprints of files to track usage" for "revision.txt"

I don't have such build step in build step dropdown.



























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-14155) Automatically select/build the latest svn tag (via List Subversion tags build params?)

2014-03-24 Thread bag...@rediffmail.com (JIRA)















































S B
 commented on  JENKINS-14155


Automatically select/build the latest svn tag (via List Subversion tags build params?)















Hi Pedro,

I am also seeing no as such option as i mentioned in this plugin ,so I am looking for the same and asking if anyone has already implemented it as I am eagerly looking for.

Best Regards,



























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-14155) Automatically select/build the latest svn tag (via List Subversion tags build params?)

2014-03-24 Thread bag...@rediffmail.com (JIRA)















































S B
 commented on  JENKINS-14155


Automatically select/build the latest svn tag (via List Subversion tags build params?)















this is the issue i raised looking for the same feature: https://issues.jenkins-ci.org/browse/JENKINS-22274 



























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] [support-core] (JENKINS-22326) Deadlock in logging















































Jesse Glick
 created  JENKINS-22326


Deadlock in logging















Issue Type:


Bug



Assignee:


Jesse Glick



Components:


support-core



Created:


24/Mar/14 4:39 PM



Description:


Observed a deadlock including a thread blocked like this:


com.cloudbees.jenkins.support.impl.JenkinsLogs$LogFile.publish
com.cloudbees.jenkins.support.impl.JenkinsLogs$CustomHandler.publish
java.util.logging.Logger.log
RedactedQueueTaskDispatcher.canTake
hudson.model.Queue$BuildableItem.canTake
hudson.model.Queue$BuildableItem.getCauseOfBlockage
hudson.model.Queue$Item.getWhy
hudson.model.Queue$Item.toString
java.text.MessageFormat.subformat
java.text.MessageFormat.format
java.text.Format.format
java.text.MessageFormat.format
java.util.logging.Formatter.formatMessage
com.cloudbees.jenkins.support.SupportLogFormatter.format
java.util.logging.StreamHandler.publish
com.cloudbees.jenkins.support.impl.JenkinsLogs$LogFile.publish


vs. another blocked like this:


com.cloudbees.jenkins.support.SupportLogFormatter.format
java.util.logging.StreamHandler.publish
com.cloudbees.jenkins.support.impl.JenkinsLogs$LogFile.publish
com.cloudbees.jenkins.support.impl.JenkinsLogs$CustomHandler.publish





Project:


Jenkins



Labels:


deadlock




Priority:


Critical



Reporter:


Jesse Glick

























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] [delivery-pipeline] (JENKINS-22283) Ability to configure the view to show implicit upstream maven projects that contribute to a given pipeline















































Patrik Boström
 updated  JENKINS-22283


Ability to configure the view to show *implicit* upstream maven projects that contribute to a given pipeline
















Could this be a way?





Change By:


Patrik Boström
(24/Mar/14 4:40 PM)




Attachment:


JENKINS-22283.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] [support-core] (JENKINS-22326) Deadlock in logging















































Jesse Glick
 started work on  JENKINS-22326


Deadlock in logging
















Change By:


Jesse Glick
(24/Mar/14 4:47 PM)




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] [delivery-pipeline] (JENKINS-22211) Parallel stages display distorted















































Patrik Boström
 commented on  JENKINS-22211


Parallel stages display distorted















Johan, I have created JENKINS-22327 for the long stage name bug.



























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] [delivery-pipeline] (JENKINS-22327) Handle longer stage names















































Patrik Boström
 created  JENKINS-22327


Handle longer stage names















Issue Type:


Bug



Assignee:


Unassigned


Components:


delivery-pipeline



Created:


24/Mar/14 4:54 PM



Description:


View should handle longer stage names.




Project:


Jenkins



Priority:


Major



Reporter:


Patrik Boström

























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] [delivery-pipeline] (JENKINS-22327) Handle longer stage names















































Patrik Boström
 updated  JENKINS-22327


Handle longer stage names
















Screnshot showing the problem





Change By:


Patrik Boström
(24/Mar/14 4:56 PM)




Attachment:


1395214255_Screen_Shot_2014-03-19_at_08.29.18.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] [support-core] (JENKINS-22326) Deadlock in logging
















































SCM/JIRA link daemon
 resolved  JENKINS-22326 as Fixed


Deadlock in logging
















Change By:


SCM/JIRA link daemon
(24/Mar/14 5:00 PM)




Status:


InProgress
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] [support-core] (JENKINS-22326) Deadlock in logging















































SCM/JIRA link daemon
 commented on  JENKINS-22326


Deadlock in logging















Code changed in jenkins
User: Jesse Glick
Path:
 src/main/java/com/cloudbees/jenkins/support/impl/JenkinsLogs.java
http://jenkins-ci.org/commit/support-core-plugin/d7af2fa1ff7d8afc4b2d4b7ac247e3c02d4e7ee7
Log:
  FIXED JENKINS-22326 Do not reuse a SupportLogFormatter across handlers.
Its lock could be held while calling toString on something which might in turn log something against another handler.





























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-21124) Use proxy to access git repository

2014-03-24 Thread y...@schli.ch (JIRA)















































Marc Günther
 commented on  JENKINS-21124


Use proxy to access git repository















Some context would be very helpful!


	What do the proxy settings in plugin manager have to do with cloning a git repository?
	Where in Jenkins is there a "validate Proxy" 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] [email-ext] (JENKINS-22312) email-ext add argument showMessage to token FAILED_TESTS

2014-03-24 Thread slide.o....@gmail.com (JIRA)















































Alex Earl
 commented on  JENKINS-22312


email-ext add argument showMessage to token FAILED_TESTS 















Sure, feel free to create a pull request.



























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-17573) Installation from jenkins-ci repository fails on Ubuntu 12.04 when jenkins is already installed















































ssbarnea
 commented on  JENKINS-17573


Installation from jenkins-ci repository fails on Ubuntu 12.04 when jenkins is already installed















Tried the workaround and remove jenkins. After this I tried to install it again but I've got 

root@smini:/etc/nginx/sites-enabled# apt-get install jenkins
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed
  jenkins
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/61.2 MB of archives.
After this operation, 67.3 MB of additional disk space will be used.
Selecting previously unselected package jenkins.
(Reading database ... 277604 files and directories currently installed.)
Unpacking jenkins (from .../archives/jenkins_1.555_all.deb) ...
Processing triggers for ureadahead ...
Setting up jenkins (1.555) ...
start: Job failed to start
invoke-rc.d: initscript jenkins, action "start" failed.
dpkg: error processing jenkins (--configure):
 subprocess installed post-installation script returned error exit status 1
No apport report written because MaxReports has already been reached
Errors were encountered while processing:
 jenkins
E: Sub-process /usr/bin/dpkg returned an error code (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] [core] (JENKINS-17573) Installation from jenkins-ci repository fails on Ubuntu 12.04 when jenkins is already installed















































ssbarnea
 updated  JENKINS-17573


Installation from jenkins-ci repository fails on Ubuntu 12.04 when jenkins is already installed
















Change By:


ssbarnea
(24/Mar/14 5:39 PM)




Priority:


Minor
Critical





Component/s:


debian-package-builder



























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-trigger] (JENKINS-22311) gerrit trigger can cause unwieldy build history when there are pending jobs

2014-03-24 Thread exgr...@gmail.com (JIRA)















































Eric Griswold
 updated  JENKINS-22311


gerrit trigger can cause unwieldy build history when there are pending jobs
















Here's a screenshot.





Change By:


Eric Griswold
(24/Mar/14 5:44 PM)




Attachment:


eric.griswold-shot-window-0x1c25fe5.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] [core] (JENKINS-22311) gerrit trigger can cause unwieldy build history when there are pending jobs

2014-03-24 Thread exgr...@gmail.com (JIRA)















































Eric Griswold
 updated  JENKINS-22311


gerrit trigger can cause unwieldy build history when there are pending jobs
















Change By:


Eric Griswold
(24/Mar/14 5:47 PM)




Assignee:


EricGriswold
rsandell





Component/s:


core



























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] [debian-package-builder] (JENKINS-22328) ubuntu switch to jenkins debian distribution fails because: subprocess installed post-installation script returned error exit status 1















































ssbarnea
 created  JENKINS-22328


ubuntu switch to jenkins debian distribution fails because: subprocess installed post-installation script returned error exit status 1















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


debian-package-builder



Created:


24/Mar/14 6:15 PM



Description:



dpkg -D5 --configure -a
Setting up jenkins (1.555) ...
+ [ -r /etc/default/jenkins ]
+ . /etc/default/jenkins
+ NAME=jenkins
+ JAVA=/usr/bin/java
+ PIDFILE=/var/run/jenkins/jenkins.pid
+ JENKINS_USER=jenkins
+ JENKINS_ROOT=/usr/share/jenkins
+ JENKINS_WAR=/usr/share/jenkins/jenkins.war
+ JENKINS_HOME=/var/lib/jenkins
+ JENKINS_RUN=/var/run/jenkins
+ RUN_STANDALONE=true
+ JENKINS_LOG=/var/log/jenkins/jenkins.log
+ MAXOPENFILES=8192
+ HTTP_PORT=
+ AJP_PORT=-1
+ HTTP_HOST=127.0.0.1
+ AJP_HOST=127.0.0.1
+ JENKINS_ARGS=--webroot=/var/run/jenkins/war --httpPort= --ajp13Port=-1 --prefix=/jenkins
+ JENKINS_ARGS=--webroot=/var/run/jenkins/war --httpPort= --ajp13Port=-1 --prefix=/jenkins --httpListenAddress=127.0.0.1 --ajp13ListenAddress=127.0.0.1
+ JENKINS_ARGS=--webroot=/var/run/jenkins/war --httpPort= --ajp13Port=-1 --prefix=/jenkins --httpListenAddress=127.0.0.1 --ajp13ListenAddress=127.0.0.1 --preferredClassLoader=java.net.URLClassLoader
+ : jenkins
+ id jenkins
+ test -d /var/lib/hudson -a ! ( -e /var/lib/hudson/.for-jenkins )
+ chown jenkins:adm /var/lib/jenkins /var/log/jenkins
+ chmod u+rwx /var/lib/jenkins /var/log/jenkins
+ chown -R jenkins:adm /var/cache/jenkins
+ chmod -R 750 /var/cache/jenkins
+ test -d /var/run/jenkins
+ chown -R jenkins:adm /var/run/jenkins
+ chmod -R 750 /var/run/jenkins
+ [ -x /etc/init.d/jenkins ]
+ [ ! -e /etc/init/jenkins.conf ]
+ invoke-rc.d jenkins start
start: Job failed to start
invoke-rc.d: initscript jenkins, action "start" failed.
+ exit 1
dpkg: error processing jenkins (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 jenkins





Environment:


1.555, ubuntu 12.04




Project:


Jenkins



Priority:


Critical



Reporter:


ssbarnea

























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] [master-slave] (JENKINS-22285) Steps for installing both Master and Slave on centos 6

2014-03-24 Thread jagan...@gmail.com (JIRA)
















































jagan M
 assigned  JENKINS-22285 to Unassigned



Steps for installing both Master and Slave on centos 6
















Change By:


jagan M
(24/Mar/14 6:14 PM)




Assignee:


KohsukeKawaguchi



























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-22085) git plugin should allow perform clone with --single-branch parameter to speed up (requires git 1.7.10+)
















































Mark Waite
 assigned  JENKINS-22085 to Mark Waite



git plugin should allow perform clone with --single-branch parameter to speed up (requires git 1.7.10+)
















Change By:


Mark Waite
(24/Mar/14 6:29 PM)




Assignee:


NicolasDeLoof
MarkWaite



























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] [crowd2] (JENKINS-13279) Interface with Crowd embedded that runs in Jira

2014-03-24 Thread gentoo.inte...@gmail.com (JIRA)















































Kanstantsin Shautsou
 commented on  JENKINS-13279


Interface with Crowd embedded that runs in Jira















Yes, but we need firstly check changes. I can merge and enable beta builds, so it become available in experimental repo.



























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] [crowd2] (JENKINS-13279) Interface with Crowd embedded that runs in Jira















































ssbarnea
 commented on  JENKINS-13279


Interface with Crowd embedded that runs in Jira















Can we have the fix for using Jira embedded user authentication. I just locked myself out of jenkins by enabling this  against Jira. Using Crowd make sense on big userbase scenarios but for small ones it only make the deployment harder.



























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-22085) git plugin should allow perform clone with --single-branch parameter to speed up (requires git 1.7.10+)

2014-03-24 Thread spamaz...@mail.ru (JIRA)















































Sergey P
 commented on  JENKINS-22085


git plugin should allow perform clone with --single-branch parameter to speed up (requires git 1.7.10+)















Thanks for suggestion, Mark! I'l check if it works as expected.



























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-19976) Cannot load a class in depended plugin after install before restart
















































SCM/JIRA link daemon
 resolved  JENKINS-19976 as Fixed


Cannot load a class in depended plugin after install before restart
















Change By:


SCM/JIRA link daemon
(24/Mar/14 7:13 PM)




Status:


InProgress
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] [core] (JENKINS-19976) Cannot load a class in depended plugin after install before restart















































SCM/JIRA link daemon
 commented on  JENKINS-19976


Cannot load a class in depended plugin after install before restart















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/java/hudson/ClassicPluginStrategy.java
 core/src/main/java/hudson/PluginManager.java
 core/src/main/java/hudson/PluginStrategy.java
 test/src/test/java/hudson/PluginManagerTest.java
http://jenkins-ci.org/commit/jenkins/56b360d6f34a1091a8bf5b73f22baca4072560ef
Log:
  JENKINS-19976 Touch-ups to PR #1054.





























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-19976) Cannot load a class in depended plugin after install before restart















































SCM/JIRA link daemon
 commented on  JENKINS-19976


Cannot load a class in depended plugin after install before restart















Code changed in jenkins
User: ikedam
Path:
 test/src/test/java/hudson/PluginManagerTest.java
http://jenkins-ci.org/commit/jenkins/38f670cf39224c40752e47e279710afeebc585e7
Log:
  JENKINS-19976 Fixed confusing comments.





























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] [support-core] (JENKINS-22326) Deadlock in logging















































SCM/JIRA link daemon
 commented on  JENKINS-22326


Deadlock in logging















Code changed in jenkins
User: Jesse Glick
Path:
 core/src/main/java/hudson/model/Queue.java
http://jenkins-ci.org/commit/jenkins/a01ebae1a4783566e42d74c4edaaf1dc3ed8a43e
Log:
  JENKINS-22326 Calling into foreign code from a toString method, like Queue.Item.getWhy → QueueTaskDispatcher, is unsafe.





























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-19976) Cannot load a class in depended plugin after install before restart















































SCM/JIRA link daemon
 commented on  JENKINS-19976


Cannot load a class in depended plugin after install before restart















Code changed in jenkins
User: ikedam
Path:
 core/src/main/java/hudson/ClassicPluginStrategy.java
 core/src/main/java/hudson/PluginManager.java
 core/src/main/java/hudson/PluginStrategy.java
http://jenkins-ci.org/commit/jenkins/87e2a7e8d5ac995a05b82c1e7839285102c111d0
Log:
  FIXED JENKINS-19976 Enable plugins to load classes from optionally depending plugins even without restarting after depended ones installed.





























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-19976) Cannot load a class in depended plugin after install before restart















































SCM/JIRA link daemon
 commented on  JENKINS-19976


Cannot load a class in depended plugin after install before restart















Code changed in jenkins
User: ikedam
Path:
 test/src/test/java/hudson/PluginManagerTest.java
http://jenkins-ci.org/commit/jenkins/536bac6425b465ad98650083ba81655265e5508f
Log:
  JENKINS-19976 Added tests how dynamic load works for @Extension.





























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-19976) Cannot load a class in depended plugin after install before restart















































SCM/JIRA link daemon
 commented on  JENKINS-19976


Cannot load a class in depended plugin after install before restart















Code changed in jenkins
User: ikedam
Path:
 test/src/test/resources/plugins/dependee.hpi
 test/src/test/resources/plugins/depender.hpi
http://jenkins-ci.org/commit/jenkins/2c047e0264a03465a3c017abf86c035a011c2479
Log:
  JENKINS-19976 Added plugins to test dynamic loading.





























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-19976) Cannot load a class in depended plugin after install before restart















































SCM/JIRA link daemon
 commented on  JENKINS-19976


Cannot load a class in depended plugin after install before restart















Code changed in jenkins
User: ikedam
Path:
 test/src/test/java/hudson/PluginManagerTest.java
http://jenkins-ci.org/commit/jenkins/8fde2e18a3a6da843d7719844e1fdd737e652c74
Log:
  JENKINS-19976 Tests for the behavior of loading a depended plugin dynamically.





























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-22278) Allow switching to a specific git revision

2014-03-24 Thread rab...@java.net (JIRA)















































raboof
 commented on  JENKINS-22278


Allow switching to a specific git revision















This indeed works perfectly, thank you!

Before closing as 'not a bug', perhaps we should make the UI a bit more clear? rename the label to 'branch/revision to build' for example?

(if it helps anything at all I'd be happy to make the change, though of course it's trivial  )



























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] [support-core] (JENKINS-22326) Deadlock in logging

2014-03-24 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-22326


Deadlock in logging















Integrated in  jenkins_main_trunk #3250
 JENKINS-22326 Calling into foreign code from a toString method, like Queue.Item.getWhy → QueueTaskDispatcher, is unsafe. (Revision a01ebae1a4783566e42d74c4edaaf1dc3ed8a43e)

 Result = SUCCESS
Jesse Glick : a01ebae1a4783566e42d74c4edaaf1dc3ed8a43e
Files : 

	core/src/main/java/hudson/model/Queue.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] [core] (JENKINS-19976) Cannot load a class in depended plugin after install before restart

2014-03-24 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-19976


Cannot load a class in depended plugin after install before restart















Integrated in  jenkins_main_trunk #3250
 FIXED JENKINS-19976 Enable plugins to load classes from optionally depending plugins even without restarting after depended ones installed. (Revision 87e2a7e8d5ac995a05b82c1e7839285102c111d0)
JENKINS-19976 Tests for the behavior of loading a depended plugin dynamically. (Revision 8fde2e18a3a6da843d7719844e1fdd737e652c74)
JENKINS-19976 Added tests how dynamic load works for @Extension. (Revision 536bac6425b465ad98650083ba81655265e5508f)
JENKINS-19976 Added plugins to test dynamic loading. (Revision 2c047e0264a03465a3c017abf86c035a011c2479)
JENKINS-19976 Fixed confusing comments. (Revision 38f670cf39224c40752e47e279710afeebc585e7)
JENKINS-19976 Touch-ups to PR #1054. (Revision 56b360d6f34a1091a8bf5b73f22baca4072560ef)

 Result = SUCCESS
devld : 87e2a7e8d5ac995a05b82c1e7839285102c111d0
Files : 

	core/src/main/java/hudson/PluginStrategy.java
	core/src/main/java/hudson/PluginManager.java
	core/src/main/java/hudson/ClassicPluginStrategy.java



devld : 8fde2e18a3a6da843d7719844e1fdd737e652c74
Files : 

	test/src/test/java/hudson/PluginManagerTest.java



devld : 536bac6425b465ad98650083ba81655265e5508f
Files : 

	test/src/test/java/hudson/PluginManagerTest.java



devld : 2c047e0264a03465a3c017abf86c035a011c2479
Files : 

	test/src/test/resources/plugins/depender.hpi
	test/src/test/resources/plugins/dependee.hpi



devld : 38f670cf39224c40752e47e279710afeebc585e7
Files : 

	test/src/test/java/hudson/PluginManagerTest.java



Jesse Glick : 56b360d6f34a1091a8bf5b73f22baca4072560ef
Files : 

	core/src/main/java/hudson/PluginManager.java
	core/src/main/java/hudson/PluginStrategy.java
	test/src/test/java/hudson/PluginManagerTest.java
	core/src/main/java/hudson/ClassicPluginStrategy.java
	changelog.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] [core] (JENKINS-22275) Save of job configuration doesn't work after removing a parameter under 'This build is parameterized'

2014-03-24 Thread jclch...@gmail.com (JIRA)















































Jeff Cheng
 commented on  JENKINS-22275


Save of job configuration doesnt work after removing a parameter under This build is parameterized















Seems to be an issue with Chrome.  With IE and Firefox, I am able to save after removing a parameter.



























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] [mail] (JENKINS-16106) Add Precedence: bulk header to notification emails

2014-03-24 Thread dpa-jenk...@aegee.org (JIRA)

Дилян Палаузов
commented on JENKINS-16106

Add Precedence: bulk header to notification emails

Setting the sender at SMTP level to is not a good idea, as the notifications about invalid email addresses, or rather addresses which were valid but are not valid anymore, will get lost. As there will be no information which addresses got invalid, notifications to those addresses will be sent forever. Some providers tend to mark sending servers as spammers, if they continuously insist to send emails to invalid addresses. This could leave to marking the emails sent from the MTA behind Jenkins to valid addresses as spam, just because the sending server is spamming, according to the rule above.

The header

Auto-Submitted: auto-generated

is enough. The last paragraph of RFC 5230 "Sieve Email Filtering: Vacation Extension", section 4.6. "Restricting Replies to Automated Processes and Mailing Lists" explicitly suppresses sending out-of-office messages to emails containing the above header.

[JIRA] [mail] (JENKINS-16106) Add Precedence: bulk header to notification emails

2014-03-24 Thread dpa-jenk...@aegee.org (JIRA)















































Дилян Палаузов
 commented on  JENKINS-16106


Add Precedence: bulk header to notification emails















About the Return-Path header, as of RFC 5321, Section 4.4. Trace Information, page 58 says, among other things:

 A message-originating SMTP system SHOULD NOT send a message that
 already contains a Return-path header field.

Effectively, the Return-Path MIME header is added by the Mail Delivery Agent, and not by the Mail Submission Agent.  Further information is spread over the whole section 4.4.



























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] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build

2014-03-24 Thread de...@ikedam.jp (JIRA)















































ikedam
 commented on  JENKINS-22212


No e-mail sent after failed build triggered from another build















Do you have multiple svn repositories to checkout?
In that case, revisions are passed as SVN_REVISION_1, SVN_REVISION_2, ... 
Please dump all environment variables by running "export" in "Execute shell".

"Record fingerprints of files to track usage" is available in Post-build Actions.



























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] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build

2014-03-24 Thread aik.b...@gmail.com (JIRA)















































Alexander Obuhovich
 commented on  JENKINS-22212


No e-mail sent after failed build triggered from another build















Do you have multiple svn repositories to checkout?

I have 2 repositories to be checked out, but I do have $SVN_REVISION environment variable never the less pointing out to SVN commit that caused build to start.

"Record fingerprints of files to track usage" is available in Post-build Actions.

That doesn't help in my case, because upstream job is triggering downstream job in parallel (non-blocking) so the downstream job starts before upstream job finishes.



























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-22301) Replace list-jobs CLI command with list-items

2014-03-24 Thread ogon...@gmail.com (JIRA)















































Oliver Gondža
 updated  JENKINS-22301


Replace list-jobs CLI command with list-items
















Change By:


Oliver Gondža
(24/Mar/14 10:51 PM)




Description:


Createmoreflexibleandwelldefinedreplacementfor{{list-jobs}}.-Print
full
itemnames
relativetoJenkins
soitcanbefedtootherCLIcommands.-
Printfulldisplaynameswhen{{--show-display-names}}used.-
Listitemsdirectlycontainedin{{View}}/{{ItemGroup}}.-Listallitemscontainedin{{View}}/{{ItemGroup}}(evenindirectly)whencalledwith{{--recursive}}.



























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-14575) SCM checkout retry count not working

2014-03-24 Thread w...@wooh.hu (JIRA)















































Adam PAPAI
 commented on  JENKINS-14575


SCM checkout retry count not working















Sent PR and this time I added a test as well. So I won't happen again hopefully.



























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-22278) Allow switching to a specific git revision















































Mark Waite
 commented on  JENKINS-22278


Allow switching to a specific git revision















Before making any change to that label text, I'd rather we wait for the completion of the work that will enable help text to be associated with that field.  I believe there is already a pull request submitted which will enable the help text on the "Branches to Build" field.  The meaning of the content of that field is more complicated than a single label can reasonably express, so I'd rather include a more verbose description in the help text.



























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-21215) Git Plugin 2.0 clones partial git config file















































Sai Anvesh Ganguri
 commented on  JENKINS-21215


Git Plugin 2.0 clones partial git config file















I am having the same issue with GIT Plugin. It clones only partially. Could anyone help me with workaround?




























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-21215) Git Plugin 2.0 clones partial git config file















































Mark Waite
 commented on  JENKINS-21215


Git Plugin 2.0 clones partial git config file















Sai Anvesh Ganguri can you better describe the conditions which cause the failure?

Can you confirm you are using the most recent versions of the git plugin and the git client 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] [parameterized-trigger] (JENKINS-22329) Single Parameter with Multiple Values















































Sai Anvesh Ganguri
 created  JENKINS-22329


Single Parameter with Multiple Values















Issue Type:


Task



Assignee:


huybrechts



Components:


parameterized-trigger, parameters



Created:


25/Mar/14 12:53 AM



Description:


Hi. I need to create an automated job in jenkins with multiple values of single parameter. Its like,

$TARGET=a,b,c,d,e (we have around 26 make targets to build)
User is required to select which targets he wants to build today. I am struck here. Is it possible this way, ok, build TARGET=a...done...then TARGET=b..done...so on
I tried different plugins, but could not get through it. Any kind of help and suggestions would be highly appreciated.




Project:


Jenkins



Priority:


Major



Reporter:


Sai Anvesh Ganguri

























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-21215) Git Plugin 2.0 clones partial git config file















































Sai Anvesh Ganguri
 commented on  JENKINS-21215


Git Plugin 2.0 clones partial git config file















Jenkins GIT Client=1.6.5
Jenkins GIT= 2.0.4
Jenkins Version=1.528



























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-21215) Git Plugin 2.0 clones partial git config file















































Sai Anvesh Ganguri
 commented on  JENKINS-21215


Git Plugin 2.0 clones partial git config file















With the GIT plugin, I could clone the repository. But, when I clone the same repository from the command line, I get the complete repository unlike the one cloned with GIT 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] [git] (JENKINS-21215) Git Plugin 2.0 clones partial git config file