[JIRA] [subversion-plugin] (JENKINS-21625) Subversion Polling does not work properly whenever using variables in the Repository URL
Tim Bradt
commented on JENKINS-21625
Subversion Polling does not work properly whenever using variables in the Repository URL
This is still a problem in Subversion plug-in 2.5...
Started on Apr 10, 2015 3:42:02 PM
ERROR: Failed to check repository revision for ${SVN_URL_ROOT}30-Dev/DatabaseBuild
org.tmatesoft.svn.core.SVNException: svn: E125002: Malformed URL '${SVN_URL_ROOT}30-Dev/DatabaseBuild'
I don't have any credential issues.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-plugin] (JENKINS-22922) Subversion : environment variables work only partially (got broken in 2.3 or prior, after 1.44)
Tim Bradt
commented on JENKINS-22922
Subversion : environment variables work only partially (got broken in 2.3 or prior, after 1.44)
This is still a problem in Subversion plug-in 2.5...
Started on Apr 10, 2015 3:42:02 PM
ERROR: Failed to check repository revision for ${SVN_URL_ROOT}30-Dev/DatabaseBuild
org.tmatesoft.svn.core.SVNException: svn: E125002: Malformed URL '${SVN_URL_ROOT}30-Dev/DatabaseBuild'
${SVN_URL_ROOT} is defined in global properties, and I do not have/need any credentials on this repo to do an update.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-plugin] (JENKINS-22568) Subversion polling not work when Repository URL value is variable - E125002: Malformed URL '${SVN_REPO_VARIABLE}'
Tim Bradt
commented on JENKINS-22568
Subversion polling not work when Repository URL value is variable - E125002: Malformed URL ${SVN_REPO_VARIABLE}
Also does not work in Subversion plugin 2.5 when defining the variables in global properties. This is already linked to JENKINS-22922 which spells that out.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-plugin] (JENKINS-27354) Error communicating to server! timeout
Alex Ehlke commented on JENKINS-27354 Error communicating to server! timeout @Patrik, here's a thread dump of master and slave (I believe slave was building a job at the moment), in another couple tabs I had the delivery pipeline view open and these GETs can be seen in the dump: https://dl.dropboxusercontent.com/u/2112716/Thread%20dump%20%5BJenkins%5D%20delivery%20pipeline%20timeout.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] [categorized-view-plugin] (JENKINS-27865) Regex not working in categorized jobs plugin
Tim Bradt commented on JENKINS-27865 Regex not working in categorized jobs plugin Critical? Anyway...You could try ^Branch\s8.2.2$, or just remove the space from your job name (replace with underscore or something). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-27898) Change Subversion plugin to allow configuration of different ways to react to working copy locked
Tim Bradt created JENKINS-27898 Change Subversion plugin to allow configuration of different ways to react to working copy locked Issue Type: Improvement Assignee: Unassigned Components: subversion-plugin Created: 10/Apr/15 8:15 PM Description: The Jenkins job/build immediately fails if the working copy is locked. For me, this is undesirable due to the structure of our repository. We have multiple builds trying to update their individual portions of the working copy. Unfortunately, svn locks the working copy one directory above the one in which the update occurs, so we get failures if multiple builds are triggered concurrently, even though they are in different sections of the repository. The way it currently works, we are notifying commiters that they have a build failure even though the changes themselves did not cause the failure, and then if they have nothing more to commit there is no choice but to MANUALLY trigger the job again. I would much prefer to have this be configurable. Let me decide if I want it to fail (current behavior), or try again every ___ seconds with ___ total attempts, other... Environment: Windows Server 2012 R2 Jenkins v1.573 Subversion Plug-in v2.5 Chrome Project: Jenkins Priority: Major Reporter: Tim Bradt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-27354) Error communicating to server! timeout
Alex Ehlke commented on JENKINS-27354 Error communicating to server! timeout I found the issue: I have a job called "Job-DSL" which is a pipeline step, it runs the Netflix Job DSL very frequently. I wasn't discarding old builds, so thousands piled up. Once I cleared the builds directory, the delivery pipeline started working (and snappily) again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-27899) Inconsistent workspace after canceling build during sync
Kevin Zellner created JENKINS-27899 Inconsistent workspace after canceling build during sync Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 10/Apr/15 9:14 PM Description: Sometimes it happens, that our workspace contains 0-sized files and the build is broken (approx. 1 of 10). This problem cannot be fixed by subsequent sync-commands, since have list is already populated with these files. We assume that this issue happens, when a build was cancelled during executing a sync command. Environment: jenkins 1.606, p4-plugin 1.2.1 Project: Jenkins Priority: Critical Reporter: Kevin Zellner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [s3-plugin] (JENKINS-27660) S3Plugin fails during upload with java.lang.IllegalArgumentException: Cannot create enum from US_EAST_1 value!
Eric Martinez commented on JENKINS-27660 S3Plugin fails during upload with java.lang.IllegalArgumentException: Cannot create enum from US_EAST_1 value! Question: How do I downgrade the S3Plugin to v0.6? I have 0.0.3 installed and it doesn't give me a downgrade option. Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-14801) Node environment variable change not recognized
Daniel Beck commented on JENKINS-14801 Node environment variable change not recognized Are all of you using Jenkins 1.477? If not, more information would be helpful. It is really unlikely that you are experiencing this old issue when you get different symptoms. https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue Read it. Seriously. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [cloudbees-folder-plugin] (JENKINS-24433) Searchbox cannot be used inside a folder
recampbell updated JENKINS-24433 Searchbox cannot be used inside a folder Change By: recampbell (10/Apr/15 10:02 PM) Labels: foldersgui lts-candidate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [sitemonitor-plugin] (JENKINS-27876) Maven builds for web sites with aggregate/ enabled don't collect unit tests
scooper4711 commented on JENKINS-27876 Maven builds for web sites with aggregate/ enabled dont collect unit tests Erroneous report. That wasn't the difference. The difference was the git pre-build step of cleaning the directory after checkout. It appears I may have found a bug in the surefire reports when aggregation is enabled. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-26520) Environment Variables BUILD_ID and BUILD_NUMBER now return the same value
Jeff Foege commented on JENKINS-26520 Environment Variables BUILD_ID and BUILD_NUMBER now return the same value This is very unfortunate. I used the Build_id and build_number as a way to tie the build to the distribution folder. It was easy for people to find the build. If this was 'not fixed' a while ago then the documentation should have gone in already. I was trying to move over to Jenkins from Hudson but now I see it will be a lot more work than I was prepared to do. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [sitemonitor-plugin] (JENKINS-27876) Maven builds for web sites with aggregate/ enabled don't collect unit tests
scooper4711 resolved JENKINS-27876 as Not A Defect Maven builds for web sites with aggregate/ enabled dont collect unit tests Change By: scooper4711 (10/Apr/15 10:03 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10629) Tar implimentation can't handle 8GB and doesn't error out.
recampbell commented on JENKINS-10629 Tar implimentation cant handle 8GB and doesnt error out. Any progress, Olaf? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-27871) Block on upstream projects does not work
Paul Draper commented on JENKINS-27871 Block on upstream projects does not work @stephenconnolly, your change fixed it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [docker-plugin] (JENKINS-27900) Custom repository when committing slave containers
Joshua Griffiths created JENKINS-27900 Custom repository when committing slave containers Issue Type: Improvement Assignee: Joshua Griffiths Components: docker-plugin Created: 11/Apr/15 12:00 AM Description: When slave containers are committed, they use the (unsanitized) job/project name as the image name (repository). The functionality to give images a custom image name which is sanitized will be very helpful. Project: Jenkins Priority: Minor Reporter: Joshua Griffiths This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [docker-plugin] (JENKINS-27900) Custom repository when committing slave containers
Joshua Griffiths started work on JENKINS-27900 Custom repository when committing slave containers Change By: Joshua Griffiths (11/Apr/15 12:01 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extra-columns-plugin] (JENKINS-27490) Extra-columns plug-in: Request for SVN_REVISION and SVN_URL columns
Fred G closed JENKINS-27490 as Wont Fix Extra-columns plug-in: Request for SVN_REVISION and SVN_URL columns Change By: Fred G (11/Apr/15 12:03 AM) Status: Open Closed Assignee: FredG RichardSpooner Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [extra-columns-plugin] (JENKINS-27490) Extra-columns plug-in: Request for SVN_REVISION and SVN_URL columns
Fred G commented on JENKINS-27490 Extra-columns plug-in: Request for SVN_REVISION and SVN_URL columns @Daniel Beck: Thanks for the additional information. @Richard Spooner: I'm afraid this request (in it's current form) can't be implemented. Nevertheless pull requests/patches are always welcome. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [docker-plugin] (JENKINS-27900) Custom repository when committing slave containers
Joshua Griffiths commented on JENKINS-27900 Custom repository when committing slave containers Addressed, pending: https://github.com/jenkinsci/docker-plugin/pull/202 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-26520) Environment Variables BUILD_ID and BUILD_NUMBER now return the same value
Steven Christou commented on JENKINS-26520 Environment Variables BUILD_ID and BUILD_NUMBER now return the same value Jeff Foege Read my comment from above. You can use the Zentimestamp plugin which will expose BUILD_TIMESTAMP environment variable. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [release-plugin] (JENKINS-27722) upgrade to the release plugin has left the plugin broken
dan tran commented on JENKINS-27722 upgrade to the release plugin has left the plugin broken tested the latest jenkins-release-plugin from source and the 'release' does not show up at navigation bar. It works when I revert it. The log does not show any error This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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.
