date:20140216
















































Jason Swager
 resolved  JENKINS-21647 as Not A Defect


In Vsphere Cloud I can not create a machine from a template
















It is expected behavior to use a Resource Pool for creation of a VM.  The alternative was to use either a Host or a Cluster AND specify a Resource Pool, which lead to issues during the UI and deployment phase if the proper values weren't chosen.  It was far more reliable and simpler with less chance of human error to just require a resource pool.





Change By:


Jason Swager
(17/Feb/14 4:18 AM)




Status:


Open
Resolved





Assignee:


Jason Swager





Resolution:


Not A Defect



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [vsphere-cloud] (JENKINS-21810) Additional options on slave disconnection
















































Jason Swager
 assigned  JENKINS-21810 to Jason Swager



Additional options on slave disconnection
















Change By:


Jason Swager
(17/Feb/14 4:12 AM)




Assignee:


Jason Swager



























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/groups/opt_out.

[JIRA] [vsphere-cloud] (JENKINS-21466) Impossible to connect to the VSphere Cloud Anymore















































Jason Swager
 commented on  JENKINS-21466


Impossible to connect to the VSphere Cloud Anymore















Also, are you using vSphere 4.1 Update 1?  Or the original vSphere 4.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/groups/opt_out.

[JIRA] [vsphere-cloud] (JENKINS-21466) Impossible to connect to the VSphere Cloud Anymore















































Jason Swager
 commented on  JENKINS-21466


Impossible to connect to the VSphere Cloud Anymore















Would you happen to have a publicly available vSphere 4.1 that I could test against?  I don't have a 4.1 system, so I can't replicate the failure.



























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/groups/opt_out.

[JIRA] [dependency-check-jenkins] (JENKINS-21762) OWASP DependencyChecker cve.2.9.h2.db still in use after successful build















































Steve Springett
 commented on  JENKINS-21762


OWASP DependencyChecker cve.2.9.h2.db still in use after successful build















Additionally, the builder step is there for convenience only - especially for use with non-build systems. Build integration should be performed by the OWASP Dependency-Check Ant task or Maven plugin, and the OWASP Dependency-Check Jenkins plugin publisher can visualize the results.



























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/groups/opt_out.

[JIRA] [vsphere-cloud] (JENKINS-21528) Can't turn on a VM
















































Jason Swager
 resolved  JENKINS-21528 as Cannot Reproduce


Can't turn on a VM
















Change By:


Jason Swager
(17/Feb/14 3:56 AM)




Status:


Open
Resolved





Resolution:


Cannot Reproduce



























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/groups/opt_out.

[JIRA] [vsphere-cloud] (JENKINS-21528) Can't turn on a VM















































Jason Swager
 commented on  JENKINS-21528


Can't turn on a VM















Closing due to no feedback from submitter.



























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/groups/opt_out.

[JIRA] [dependency-check-jenkins] (JENKINS-21762) OWASP DependencyChecker cve.2.9.h2.db still in use after successful build















































Steve Springett
 commented on  JENKINS-21762


OWASP DependencyChecker cve.2.9.h2.db still in use after successful build















It appears Jenkins tried to delete the workspace when it was still being accessed by Dependency-Check plugin.

By default, Dependency-Check Jenkins plugin will create the data directory inside the projects workspace. This can be overwritten when defining the data directory in the advanced configuration for the job. 

Specifying a data directory outside the project's workspace has the additional benefit of being able to be shared by multiple Dependency-Check jobs on the same slave machine, saving both processing power and disk space.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [dependency-check-jenkins] (JENKINS-21762) OWASP DependencyChecker cve.2.9.h2.db still in use after successful build
















































Steve Springett
 resolved  JENKINS-21762 as Not A Defect


OWASP DependencyChecker cve.2.9.h2.db still in use after successful build
















Change By:


Steve Springett
(17/Feb/14 3:54 AM)




Status:


Open
Resolved





Resolution:


Not A Defect



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [dependency-check-jenkins] (JENKINS-21758) Extra extensions should be scanned















































Steve Springett
 started work on  JENKINS-21758


Extra extensions should be scanned
















Change By:


Steve Springett
(17/Feb/14 3:47 AM)




Status:


Open
In Progress



























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/groups/opt_out.

[JIRA] [dependency-check-jenkins] (JENKINS-20564) Analysis on Jenkins slave is 10/100 time slower than on Master















































Steve Springett
 updated  JENKINS-20564


Analysis on Jenkins slave is 10/100 time slower than on Master
















Change By:


Steve Springett
(17/Feb/14 3:46 AM)




Status:


Reopened
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/groups/opt_out.

[JIRA] [dependency-check-jenkins] (JENKINS-20564) Analysis on Jenkins slave is 10/100 time slower than on Master
















































Steve Springett
 resolved  JENKINS-20564 as Cannot Reproduce


Analysis on Jenkins slave is 10/100 time slower than on Master
















Change By:


Steve Springett
(17/Feb/14 3:46 AM)




Status:


Open
Resolved





Resolution:


Cannot Reproduce



























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/groups/opt_out.

[JIRA] [dependency-check-jenkins] (JENKINS-21758) Extra extensions should be scanned















































Steve Springett
 commented on  JENKINS-21758


Extra extensions should be scanned















This will be added to the next release



























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/groups/opt_out.

[JIRA] [dependency-check-jenkins] (JENKINS-21757) Make use of Maven dependencies inside DC plugin when executing a maven job
















































Steve Springett
 resolved  JENKINS-21757 as Won't Fix


Make use of Maven dependencies inside DC plugin when executing a maven job
















Not possible to implement due to Jenkins plugin API restrictions.





Change By:


Steve Springett
(17/Feb/14 3:34 AM)




Status:


Open
Resolved





Resolution:


Won't Fix



























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/groups/opt_out.

[JIRA] [dependency-check-jenkins] (JENKINS-21757) Make use of Maven dependencies inside DC plugin when executing a maven job

Steve Springett
commented on JENKINS-21757

Make use of Maven dependencies inside DC plugin when executing a maven job

The builder step of the Dependency-Check Jenkins plugin is there for convenience. Build integration should be performed using the Ant or Maven plugin.

However, I've done some preliminary research and it does not appear that this feature is possible, as Dependency-Check maven usage requires org.apache.maven.project.MavenProject and org.apache.maven.artifact.Artifact.

In a org.apache.maven.project.MavenProject, a list of org.apache.maven.artifact.Artifact can be obtained by calling getArtifacts(). This returns a list of all dependencies for the MavenProject including a File object reference to the file - not just metadata.

By contrast, Jenkins will expose a Maven build via a plugin that extends AbstractBuild like this:

MavenModuleSetBuild mavenBuild = (MavenModuleSetBuild)build;
MavenModuleSet mavenModuleSet = mavenBuild.getProject();
Collection mavenModules = mavenModuleSet.getModules();
for (MavenModule mavenModule: mavenModules) {
/**
There is no method to retrieve a Collection of , even though a Set of them are defined. Additionally, ModuleDependency only contains artifactid, groupid and version metadata without any reference to the file on the filesystem.
*/
}

There are methods to retrieve artifacts created as a result of a Maven/Jenkins job and methods to retrieve artifacts that have been archived as a result of a Jenkins job, but there doesn't appear to be any way to retrieve org.apache.maven.artifact.Artifact from a org.apache.maven.project.MavenProject using a plugin.

This functionality will have to be requested to the Jenkins core team.

Outstanding question posted to mailing list:
https://groups.google.com/forum/#!topic/jenkinsci-dev/5Of5P8YsPMY

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/groups/opt_out.

[JIRA] [core] (JENKINS-20204) Latest release of Java 7 blocks the connection to slaves due to no permissions attribute in the JAR file

2014-02-16 Thread blo...@gmail.com (JIRA)















































Nick Newell
 commented on  JENKINS-20204


Latest release of Java 7 blocks the connection to slaves due to no permissions attribute in the JAR file















Mark W's suggestion is the best work-around for now.  



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [core] (JENKINS-10258) Allow users unicity

2014-02-16 Thread overby...@hotmail.com (JIRA)















































Paul Blundell
 commented on  JENKINS-10258


Allow users unicity















We have this issue in that there are two Jenkins users for 1 person, 1 that has logged in using credentials and one that has committed a change.

Would be nice to merge these two people into the one human they are.



























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/groups/opt_out.

[JIRA] [ci-game] (JENKINS-21824) Ability to cap the max score for the day

2014-02-16 Thread overby...@hotmail.com (JIRA)

Paul Blundell
created JENKINS-21824

Ability to cap the max score for the day

Issue Type:

New Feature

Assignee:

redsolo

Components:

ci-game

Created:

16/Feb/14 10:37 PM

Description:

It would be great if the scoring system allowed you to pick a cap number i.e. 100 and that was the maximum points a user could get for 1 check-in / 1 project / 1 day.

StackOverflow has a similar cap in that if 5 people up vote your question if within 12 hours more people upvote your quesstion, you do not gain any more points. Something like that.

The reasoning behind this is, when people check-in a legacy project they instantly get something like -5000 points. Also if someone add's a source code library that can also come with the same issues. Then the opposite can also occur - if somebody formats the imported library source code to our standards (fixing the checkstyles for line length etc) they will get +5000 which is just not cricket.

Project:

Jenkins

Priority:

Major

Reporter:

Paul Blundell

[JIRA] [parameterized-remote-trigger] (JENKINS-21470) File Based List of Parameters

2014-02-16 Thread morfi...@gmail.com (JIRA)















































Maurice W.
 commented on  JENKINS-21470


File Based List of Parameters















This will be coming soon (hopefully by Monday).

You will have the ability to specify a file path (relative from the jobs workspace) to a file which contains the parameters.

The file can be any extension, but must contain only 1 key-value pair per file and sure the equals sign ("=")as the key-pair delimiter (basically, just as it exits in the job-specific one today)



























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/groups/opt_out.

[JIRA] [ssh-slaves] (JENKINS-7641) Slaves hang when archiving artifacts

2014-02-16 Thread paul.sokolov...@linaro.org (JIRA)

Paul Sokolovsky
commented on JENKINS-7641

Slaves hang when archiving artifacts

Ok, so this is probably as old as Jenkins itself, and probably ready to become (if not already) its businesscard - what's that Jenkins thing? Ah, it does some CI and bunch of server hanging around. And the biggest problem is not that the issue described here happens, it's what shown by this log:

01:53:56.709 Archiving artifacts
12:02:21.094 ERROR: Failed to archive artifacts: *.sum
12:02:21.096 hudson.util.IOException2: hudson.util.IOException2: Failed to extract /home/buildslave/workspace/cbuild/transfer of 1 files
12:02:21.096 Caused by: java.io.IOException
12:02:21.096 at hudson.remoting.FastPipedInputStream.read(FastPipedInputStream.java:175)

So, it hanged build server for 10hrs. As it usually happens, there're more jobs accumulate for this build slave, other builds waiting for this build to complete, so entire CI system comes to a halt, followed by kaboom. And if nobody's looking, Jenkins will happily and shamelessly lock up your servers for days.

So, why this happens? Surely, there's no single reason, but carefully selected assorti of toxic stuff:

1. Bugs in JVM/Java - just because there're comments above that switching to another JDK version/provider seem to alleviate it.
2. Bugs in Jenkins - just because every new release brings only security fixes as if previous version was something like 0.0.1, so you may imagine there's lot to fix yet.
3. But most importantly, that's the way Jenkins is written. To illustrate that, let's look at linked JENKINS-11586, comment straight from Kohsuke: "The ping currently is supposed to wait for 4 minutes before it gives up and kills the channel. But I have a hard time believing that the channel did really clog for 4 minutes." Here we go. Network over which that channel goes is UNRELIABLE. Everything you find hard to believe about it is actually true. It may fail to deliver stuff, it may clog for 4 or 40 minutes, RIAA may knock on your door telling you download forbidden torrents which you never did. Or take another example, straight from FastPipedInputStream.java as quoted in stacktrace above. In its header, it confesses to be java.io.PipedInputStream equivalent, which just "uses proper synchronization" and "doesn't rely on polling". A seasonal engineer would recognize smartness and forthlooking of Java engineers who did not trust Java to do synchronization and instead used strings-and-stick method. Now smart kids came who thought they could make it better, and now their code locks up servers throughout the world.

Ok, enough intro to problem area. Let's look straight into FastPipedInputStream.java:175 which was caught red-handed in the stacktrace above: https://github.com/jenkinsci/remoting/blob/master/src/main/java/hudson/remoting/FastPipedInputStream.java#L163
And what we see immediately is infinite loop. Just see yourself: it blocks in wait on buffer for 10s, then does some liveness checks (which, as we already learned, will fail to detect any issues regularly), the checks for updates from outside, and if nothing happens, it will hang there forever. Here it is, Jenkins coding style.

Here's the patch: https://github.com/pfalcon/remoting/commit/239b3dcf26498ff296fabf770dffc7a456b2878c

So, why am I writing all this? Over time, I learned that if people come to me with artifact archiving issues, the best thing I can suggest them is AVOID NATIVE JENKINS ARTIFACT ARCHIVING LIKE A PLAGUE. People listen, and that job whose stack trace is quoted above is no longer uses it (rest of our jobs didn't use it for years). So, while I hacked up the patch above, I don't really have sandbox to test it with. So, if you experience this issue, I encourage you to try that patch and share results. Just to clarify - the patch above is not going to fix this issue (if you want it not fail, then Java and Jenkins are wrong technologies). But instead it makes it fail fast and not waste the resources (it also addresses only one infinite loop, I'm sure there're dozens more).

The stacktrace above happened with Jenins 1.532.1 on Linux/Ubuntu master/slave (x86, x64, arm slaves affected).

Thanks for listening to the rant, and happy (or sour) Jenkinsing!

This message is automatically generated by JIRA.
If you think it was sent incorrectly, ple

[JIRA] [maven2] (JENKINS-959) hudson deploys maven artifact even if test has failed

2014-02-16 Thread bpodgur...@gmail.com (JIRA)















































Benjamin Podgursky
 commented on  JENKINS-959


hudson deploys maven artifact even if test has failed















I can look but unless I'm misunderstanding, that's a solution to a different problem.  

The problem here is that jenkins is setting maven.test.failure.ignore=true, so if even in a single-module build your "goals and options" are set to "deploy", if the tests fail the build will still deploy.  Setting maven.test.failure.ignore=false does prevent this behavior, but it's very inconvenient because it has to be set per-project (I can't find a way to set it globally) and the fact that it's not a default means we didn't notice this until we noticed jenkins had deployed functionally-broken artifacts. 



























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/groups/opt_out.

[JIRA] [core] (JENKINS-21292) Do not attempt to parse blank responses from cancelled XHR POST requests















































SCM/JIRA link daemon
 commented on  JENKINS-21292


Do not attempt to parse blank responses from cancelled XHR POST requests















Code changed in jenkins
User: Greg Inozemtsev
Path:
 core/src/main/resources/hudson/model/BuildTimelineWidget/control.jelly
http://jenkins-ci.org/commit/jenkins/4ea919c5bb138cab00c70eed6be33f6337e08bfa
Log:
  JENKINS-21292 Do not attempt to parse blank responses from cancelled XHR POST requests

An XHR POST request may be cancelled by navigating away from the page while the timeline is loading.  This causes alert spam on Chrome and Safari.
(cherry picked from commit 72bb47731fda65c4b27e5e12e1942e5c44738145)





























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/groups/opt_out.

[JIRA] [junit] (JENKINS-7866) junit report test count graph has wrong colours















































SCM/JIRA link daemon
 commented on  JENKINS-7866


junit report test count graph has wrong colours















Code changed in jenkins
User: Chris Arnott
Path:
 core/src/main/java/hudson/tasks/junit/History.java
http://jenkins-ci.org/commit/jenkins/4a6e59b34b792946a65f9907c40e14a300814f68
Log:
  JENKINS-7866 - Fix failed tests displaying as Yellow on "History for Test Results" page.

The colours where added in a different order to the data, resulting in failed tests displying as yellow and skipped tests displaying as red.

(cherry picked from commit 7ef1d37730997a06386670c343782e55fe4c029f)





























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/groups/opt_out.

[JIRA] [core] (JENKINS-21639) Jobs named "." can be created, but not built, configured, accessed, ...















































SCM/JIRA link daemon
 commented on  JENKINS-21639


Jobs named "." can be created, but not built, configured, accessed, ...















Code changed in jenkins
User: Daniel Beck
Path:
 core/src/main/java/jenkins/model/Jenkins.java
http://jenkins-ci.org/commit/jenkins/fec6b41b74d7ece48ae2afbdfb995b377d4094ea
Log:
  [FIXED JENKINS-21639] Prevent creation of job named '.'.

(cherry picked from commit 780b38bc755028f4c4d72378896407a182bd5b30)





























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/groups/opt_out.

[JIRA] [core] (JENKINS-21457) Replace description in error dialog instead of appending















































SCM/JIRA link daemon
 commented on  JENKINS-21457


Replace description in error dialog instead of appending















Code changed in jenkins
User: Oliver Gondža
Path:
 core/src/main/resources/lib/form/apply/apply.js
http://jenkins-ci.org/commit/jenkins/ec071eea6ce2cf1bb034eebdc79795a59e3b9940
Log:
  [FIXED JENKINS-21457] Replace description in error dialog instead of appending

(cherry picked from commit 581024ba0a4d4e68feb6b3cc7137015768b33520)





























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/groups/opt_out.

[JIRA] [core] (JENKINS-20345) ZIP file download generates corrupt zip file