[JIRA] [build-with-parameters] (JENKINS-19210) The problem with parameterized build and subversion plugin
Oleg Nenashev commented on JENKINS-19210 The problem with parameterized build and subversion plugin @Veronika Could you update the issue by evaluation 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/d/optout.
[JIRA] [junit] (JENKINS-22383) Failure found during the build process of RTRT using windows batch command
Oleg Nenashev updated JENKINS-22383 Failure found during the build process of RTRT using windows batch command Change By: Oleg Nenashev (02/Jun/14 7:12 AM) Component/s: junit Component/s: subversion This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-22383) Failure found during the build process of RTRT using windows batch command
Oleg Nenashev resolved JENKINS-22383 as Incomplete Failure found during the build process of RTRT using windows batch command Most probably, RTRT tool produces non-JUnit output. Please attach the report file and reopen the issue if it stills actual Change By: Oleg Nenashev (02/Jun/14 7:14 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-23266) GitSCM rebuilds all the time while using poll scm
sashas83
created JENKINS-23266
GitSCM rebuilds all the time while using poll scm
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
git, git-client
Created:
02/Jun/14 7:13 AM
Description:
Reproduction scenrario:
create 2 remote branches in "origin"
1) 1 - called bug/namespace/master
2) 2 - called namespace/master
Setup the projec to poll scm (every minute) and to build the branch namespace/master.
Expected result: if there are no changes in namespace/master it wont get rebuilt.
Actual: branch is constantly rebuilt
the problem is in git-client since the command
git ls-remote namespace/master will return you both branch revisions and take the first one ..
buggy method is :
CliGitAPIImpl:
public ObjectId getHeadRev(String url, String branchSpec) throws GitException, InterruptedException {
final String branchName = extractBranchNameFromBranchSpec(branchSpec);
ArgumentListBuilder args = new ArgumentListBuilder("ls-remote");
args.add("-h");
StandardCredentials cred = credentials.get(url);
if (cred == null) cred = defaultCredentials;
args.add(url);
args.add(branchName);
String result = launchCommandWithCredentials(args, null, cred, url);
return result.length()>=40 ? ObjectId.fromString(result.substring(0, 40)) : null;
}
Project:
Jenkins
Priority:
Major
Reporter:
sashas83
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-22383) Failure found during the build process of RTRT using windows batch command
Oleg Nenashev edited a comment on JENKINS-22383 Failure found during the build process of RTRT using windows batch command Most probably, RTRT tool produces a non-JUnit output. Please attach the report file and reopen the issue if it stills actual This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-21123) Macro for PIPELINE_VERSION
Patrik Boström resolved JENKINS-21123 as Fixed Macro for PIPELINE_VERSION Fixed. https://github.com/Diabol/delivery-pipeline-plugin/commit/62ef6b14cdceca21a533b530970f5ec10300fd5d Change By: Patrik Boström (02/Jun/14 7:53 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-21123) Macro for PIPELINE_VERSION
Patrik Boström assigned JENKINS-21123 to Patrik Boström Macro for PIPELINE_VERSION Change By: Patrik Boström (02/Jun/14 7:52 AM) Assignee: 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] [cli] (JENKINS-23248) CLI: get-job calls are causing file descriptor leaks.
Craig Phillips commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. 1.564 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp] (JENKINS-22848) Hockeyapp plugin can't publish from remote slaves
Oliver H edited a comment on JENKINS-22848 Hockeyapp plugin can't publish from remote slaves Got it released with: mvn org.apache.maven.plugins:maven-release-plugin:2.5:perform -DrepositoryId=maven.jenkins-ci.org Version 1.1.0 should be available within the next hours. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp] (JENKINS-22848) Hockeyapp plugin can't publish from remote slaves
Oliver H commented on JENKINS-22848 Hockeyapp plugin can't publish from remote slaves Got it release with: mvn org.apache.maven.plugins:maven-release-plugin:2.5:perform -DrepositoryId=maven.jenkins-ci.org Version 1.1.0 should be available within the next hours. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-22817) Bug in role strategy plugin
Oleg Nenashev resolved JENKINS-22817 as Incomplete Bug in role strategy plugin Now response from the submitter... Change By: Oleg Nenashev (02/Jun/14 8:57 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23248) CLI: get-job calls are causing file descriptor leaks.
Craig Phillips commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. Just upgraded to 1.565 and the issue still persists. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [www] (JENKINS-263) Preserve build order of downstream projects
Tim Pizey commented on JENKINS-263 Preserve build order of downstream projects Oleg, As Kosuke says above: it is. The list of downstream jobs should be represented as a list and executed in order specified. Reordering alphabetically is a 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] [www] (JENKINS-263) Preserve build order of downstream projects
Tim Pizey edited a comment on JENKINS-263 Preserve build order of downstream projects Oleg, As Kohsuke says above: it is. The list of downstream jobs should be represented as a list and executed in order specified. Reordering alphabetically is a 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] [core] (JENKINS-21089) archiving artefacts from beaglebone fails
Steve Osselton commented on JENKINS-21089 archiving artefacts from beaglebone fails Have upgraded the Beaglebone to Ubuntu 14.04 and everything now works ok. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [config-rotator] (JENKINS-22832) Unable to create view when stream exists ( our case 11220 )
Mads Nielsen resolved JENKINS-22832 as Fixed Unable to create view when stream exists ( our case 11220 ) Change By: Mads Nielsen (02/Jun/14 9:38 AM) Status: Open Resolved Fix Version/s: current 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] [xvfb] (JENKINS-23267) NullPointerException in XvfbBuildWrapper.setUp
Alexander Clausen
created JENKINS-23267
NullPointerException in XvfbBuildWrapper.setUp
Issue Type:
Bug
Assignee:
zregvart
Components:
xvfb
Created:
02/Jun/14 9:41 AM
Description:
I get the following traceback when running a job with configured xvfb plugin:
FATAL: null
java.lang.NullPointerException
at org.jenkinsci.plugins.xvfb.XvfbBuildWrapper.setUp(XvfbBuildWrapper.java:568)
at hudson.model.Build$BuildExecution.doRun(Build.java:153)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518)
at hudson.model.Run.execute(Run.java:1706)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:231)
The line reads:
if (assignedLabels != null || assignedLabels.trim().isEmpty()) {
shouldn't that be && ?
Project:
Jenkins
Labels:
plugin
xvfb
Priority:
Major
Reporter:
Alexander Clausen
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-263) Preserve build order of downstream projects
Oleg Nenashev commented on JENKINS-263 Preserve build order of downstream projects @Tim I've reopened the issue and set the proper component This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-263) Preserve build order of downstream projects
Oleg Nenashev reopened JENKINS-263 Preserve build order of downstream projects Change By: Oleg Nenashev (02/Jun/14 9:49 AM) Resolution: Fixed 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] [core] (JENKINS-263) Preserve build order of downstream projects
Oleg Nenashev updated JENKINS-263 Preserve build order of downstream projects Change By: Oleg Nenashev (02/Jun/14 9:48 AM) Issue Type: New Feature 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] [core] (JENKINS-263) Preserve build order of downstream projects
Oleg Nenashev updated JENKINS-263 Preserve build order of downstream projects Change By: Oleg Nenashev (02/Jun/14 9:49 AM) Component/s: core Component/s: www This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvfb] (JENKINS-23267) NullPointerException in XvfbBuildWrapper.setUp when configured without node label restrictions
Alexander Clausen
updated JENKINS-23267
NullPointerException in XvfbBuildWrapper.setUp when configured without node label restrictions
Change By:
Alexander Clausen
(02/Jun/14 10:00 AM)
Summary:
NullPointerException in XvfbBuildWrapper.setUp
when configured without node label restrictions
Description:
I get the following traceback when running a job with configured xvfb plugin
and no node labels
:FATAL: nulljava.lang.NullPointerException at org.jenkinsci.plugins.xvfb.XvfbBuildWrapper.setUp(XvfbBuildWrapper.java:568) at hudson.model.Build$BuildExecution.doRun(Build.java:153) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518) at hudson.model.Run.execute(Run.java:1706) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231)The line reads:if (assignedLabels != null || assignedLabels.trim().isEmpty()) {shouldn't that be && ?
A workaround is adding a label (i.e. master)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
HID BULB quotation from china factory 2015-6-2 18:01:39
HelloSirGooddayThisisRenee,IamthesalesmanagerfromChinaAUTOBULB=manufacturer-Jiaxingmeiyaolightingtechnologyco.,ltd.Wearethem=akerofHIDautobulbsinceyear2008.Ifyouhaveinterestedinthis=products,welcomecontactusforgettingmoreinformation,andifyo=uarenotinthisbusiness,Ifeelsorrytobotheryou,becauseIjust=searchthebuyerinformationoninternet. OurcompanylocatedInZhejiangProvinceChina,currently=wehavematuretechnologyinhidmaking,sowecouldsupplyourcusto=merwithhighqualitylongwarrantyandcompetitivepriceforourauto=bulb.Wehavefullmodelfocusondifferentcar,alsowithcolorte=mperaturefrom3000Kto3K. Plscontactuswithyourdetailsrequest,wewillgiveyou=thequotationfocusonyourneed. Thankyou&bestregards Renee -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22800) Downstream build does not wait for upstream build to complete
Benjamin Ernst
updated JENKINS-22800
Downstream build does not wait for upstream build to complete
Change By:
Benjamin Ernst
(02/Jun/14 10:07 AM)
Description:
Hi, we have found an issue in our build pipeline. We are using Jenkins ver. 1.532.3The setup is as follows:* The master does not execute builds* There are multiple slave nodes connected to the master. All builds are executed on the slaves* Job A** is polling for SCM** is set to have a quiet period of 10 seconds** on build, is generating an artifact* Job B** is polling for SCM** is set to have a quiet period of 10 seconds** is set to be dependent on Job A ("Build after other projects are built")** is set to not build when upstream jobs are building ("Block build when upstream project is building")** on build, downloads $HUDSON_URL/job/A/lastSuccessfulBuild/[path-to-artifact]/artifact.zipGiven that* Job A's last successful build is #9* Job B's last successful build is #19*
-
User Eve checks in files to a location observed by both jobs
-
* User Eve checks in files such that both jobs will detect an SCM change
We can now observe the following sequence of events:# Job A observes the changes and triggers build #10 that is put into the waiting queue# Job B observes the changes and triggers build #20 that is put into the waiting queue# The quiet period elapses, job A build #10 starts to build# Job A build #10 is finished generating the artifact, it is uploaded to the master# Job A build #10 tries to trigger a new build of Job B. Job B build #20 is already in the waiting queue, so no new build is triggered# Job A build #10 does not complete for the next 30 seconds. we believe this is due to uploading the build log to the master, but we are uncertain about this.# {color:red}Job B build #20 starts to build{color}# {color:red}Job B build #20 downloads $HUDSON_URL/job/A/lastSuccessfulBuild/[path-to-artifact]/artifact.zip (lastSuccessfulBuild seems to point to Job A build #9 at this time){color}# Job A completes with the message "Finished: SUCCESS"
# No more builds of Jobs A and B are pending/will be running
We are uncertain whether the problem lies in step 7 or step 8. Our requirement is that Job B build #20 downloads the artifact of the last succeeded build of job A, which should be build #10. This seems like a bug to us.This issue seems related to JENKINS-5125. [Looking at the source code|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Job.java#L286] reveals that this code fragment proposed in JENKINS-5125 is not implemented:{code}public boolean isBuilding() {RunT b = getLastBuild();return b!=null && b.isLogUpdated();}{code}We think there might be a chance that implementing this code fragment would also fix our issue.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-22800) Downstream build does not wait for upstream build to complete
Benjamin Ernst
updated JENKINS-22800
Downstream build does not wait for upstream build to complete
Change By:
Benjamin Ernst
(02/Jun/14 10:09 AM)
Description:
Hi, we have found an issue in our build pipeline. We are using Jenkins ver. 1.532.3The setup is as follows:* The master does not execute builds* There are multiple slave nodes connected to the master. All builds are executed on the slaves* Job A** is polling for SCM** is set to have a quiet period of 10 seconds** on build, is generating an artifact* Job B** is polling for SCM** is set to have a quiet period of 10 seconds** is set to be dependent on Job A ("Build after other projects are built")** is set to not build when upstream jobs are building ("Block build when upstream project is building")** on build, downloads $HUDSON_URL/job/A/lastSuccessfulBuild/[path-to-artifact]/artifact.zipGiven that* Job A's last successful build is #9* Job B's last successful build is #19* -User Eve checks in files to a location observed by both jobs- * User Eve checks in files such that both jobs will detect an SCM changeWe can now observe the following sequence of events:# Job A observes the changes and triggers build #10 that is put into the waiting queue# Job B observes the changes and triggers build #20 that is put into the waiting queue# The quiet period elapses, job A build #10 starts to build# Job A build #10 is finished generating the artifact, it is uploaded to the master# Job A build #10 tries to trigger a new build of Job B. Job B build #20 is already in the waiting queue, so no new build is triggered#
-
Job A build #10 does not complete for the next 30 seconds. we believe this is due to uploading the build log to the master, but we are uncertain about this.
- (correction: it was due to the disk usage plugin, which we now removed. There is no noticable delay anymore, but the problem described here persists)
# {color:red}Job B build #20 starts to build{color}# {color:red}Job B build #20 downloads $HUDSON_URL/job/A/lastSuccessfulBuild/[path-to-artifact]/artifact.zip (lastSuccessfulBuild seems to point to Job A build #9 at this time){color}# Job A completes with the message "Finished: SUCCESS"#
Job B completes with the message "Finished: SUCCESS"#
No more builds of Jobs A and B are pending/will be runningWe are uncertain whether the problem lies in step 7 or step 8. Our requirement is that Job B build #20 downloads the artifact of the last succeeded build of job A, which should be build #10. This seems like a bug to us.This issue seems related to JENKINS-5125. [Looking at the source code|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Job.java#L286] reveals that this code fragment proposed in JENKINS-5125 is not implemented:{code}public boolean isBuilding() {RunT b = getLastBuild();return b!=null && b.isLogUpdated();}{code}We think there might be a chance that implementing this code fragment would also fix our issue.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-22800) Downstream build does not wait for upstream build to complete
Benjamin Ernst
commented on JENKINS-22800
Downstream build does not wait for upstream build to complete
@bruce_rust: You said:
Job B is triggered off of a SCM poll and so gets the latest Job A build at the time (which is build 9)
This is in contrary to:
Job B
is set to be dependent on Job A ("Build after other projects are built")
is set to not build when upstream jobs are building ("Block build when upstream project is building")
Job B may be triggered, as you say, off of an SCM poll, while Job A is building, but then the Build of Job B must remain in the wait queue. Job B is set to have the two properties above, so it must not start while Job A is running. No matter how many SCM polls/hooks/triggers there are.
I corrected small things pointing into this direction in the story description. If you think I misread what you meant, I kindly ask you to clarify it referring to this comment.
For your reference, the repositories of Job A and Job B are completely different. But from my point of view this does influence the core issue here, that is, Build B starts before Build A is completely finished.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-263) Preserve build order of downstream projects
Tim Pizey commented on JENKINS-263 Preserve build order of downstream projects @Oleg great This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-19852) NPE during submission of EnvInject JobProperty configurations
SCM/JIRA link daemon commented on JENKINS-19852 NPE during submission of EnvInject JobProperty configurations Code changed in jenkins User: Nicolas De loof Path: src/main/java/org/jenkinsci/plugins/envinject/EnvInjectJobProperty.java http://jenkins-ci.org/commit/envinject-plugin/e92085799b2d04f34a689e31784b6c5292a60456 Log: [FIXED JENKINS-19852] This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-19852) NPE during submission of EnvInject JobProperty configurations
SCM/JIRA link daemon resolved JENKINS-19852 as Fixed NPE during submission of EnvInject JobProperty configurations Change By: SCM/JIRA link daemon (02/Jun/14 10:33 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-22800) Downstream build does not wait for upstream build to complete
Benjamin Ernst
updated JENKINS-22800
Downstream build does not wait for upstream build to complete
Change By:
Benjamin Ernst
(02/Jun/14 10:42 AM)
Description:
Hi, we have found an issue in our build pipeline. We are using Jenkins ver. 1.
532
554
.
3
1
The setup is as follows:* The master does not execute builds* There are multiple slave nodes connected to the master. All builds are executed on the slaves* Job A** is polling for SCM** is set to have a quiet period of 10 seconds** on build, is generating an artifact* Job B** is polling for SCM** is set to have a quiet period of 10 seconds** is set to be dependent on Job A ("Build after other projects are built")** is set to not build when upstream jobs are building ("Block build when upstream project is building")** on build, downloads $HUDSON_URL/job/A/lastSuccessfulBuild/[path-to-artifact]/artifact.zipGiven that* Job A's last successful build is #9* Job B's last successful build is #19* -User Eve checks in files to a location observed by both jobs- * User Eve checks in files such that both jobs will detect an SCM changeWe can now observe the following sequence of events:# Job A observes the changes and triggers build #10 that is put into the waiting queue# Job B observes the changes and triggers build #20 that is put into the waiting queue# The quiet period elapses, job A build #10 starts to build# Job A build #10 is finished generating the artifact, it is uploaded to the master# Job A build #10 tries to trigger a new build of Job B. Job B build #20 is already in the waiting queue, so no new build is triggered# -Job A build #10 does not complete for the next 30 seconds. we believe this is due to uploading the build log to the master, but we are uncertain about this.- (correction: it was due to the disk usage plugin, which we now removed. There is no noticable delay anymore, but the problem described here persists)# {color:red}Job B build #20 starts to build{color}# {color:red}Job B build #20 downloads $HUDSON_URL/job/A/lastSuccessfulBuild/[path-to-artifact]/artifact.zip (lastSuccessfulBuild seems to point to Job A build #9 at this time){color}# Job A completes with the message "Finished: SUCCESS"# Job B completes with the message "Finished: SUCCESS"# No more builds of Jobs A and B are pending/will be runningWe are uncertain whether the problem lies in step 7 or step 8. Our requirement is that Job B build #20 downloads the artifact of the last succeeded build of job A, which should be build #10. This seems like a bug to us.This issue seems related to JENKINS-5125. [Looking at the source code|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Job.java#L286] reveals that this code fragment proposed in JENKINS-5125 is not implemented:{code}public boolean isBuilding() {RunT b = getLastBuild();return b!=null && b.isLogUpdated();}{code}We think there might be a chance that implementing this code fragment would also fix our issue.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-22800) Downstream build does not wait for upstream build to complete
Benjamin Ernst commented on JENKINS-22800 Downstream build does not wait for upstream build to complete I changed the "affected version" in my description to 1.554.1, as we've updated and can still observe the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh] (JENKINS-23231) Add timeout config for SSH plugins
Amo Chumber commented on JENKINS-23231 Add timeout config for SSH plugins It would (I believe) allow me to avoid or reduce occurrences of the error below. I'm not sure if Jenkins passes a value or if it uses the library default but I get this error almost immediately suggesting the value used (whichever that is) is set very low. [SSH] Exception:timeout: socket is not established com.jcraft.jsch.JSchException: timeout: socket is not established at com.jcraft.jsch.Util.createSocket(Util.java:386) at com.jcraft.jsch.Session.connect(Session.java:182) at com.jcraft.jsch.Session.connect(Session.java:150) at org.jvnet.hudson.plugins.SSHSite.createSession(SSHSite.java:141) at org.jvnet.hudson.plugins.SSHSite.executeCommand(SSHSite.java:151) at org.jvnet.hudson.plugins.SSHBuilder.perform(SSHBuilder.java:60) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:745) at hudson.model.Build$BuildExecution.build(Build.java:198) at hudson.model.Build$BuildExecution.doRun(Build.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518) at hudson.model.Run.execute(Run.java:1706) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Build step 'Execute shell script on remote host using ssh' marked build as 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/d/optout.
[JIRA] [clearcase-ucm] (JENKINS-23268) Long version FQN can generate error on windows (our case 11125)
Mads Nielsen created JENKINS-23268 Long version FQN can generate error on windows (our case 11125) Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: clearcase-ucm Created: 02/Jun/14 11:39 AM Fix Versions: current Project: Jenkins Priority: Minor Reporter: Mads Nielsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-user-vars] (JENKINS-23269) NPE when getting upstreambuild after starting a rebuild
Sven Appenrodt
created JENKINS-23269
NPE when getting upstreambuild after starting a rebuild
Issue Type:
Bug
Assignee:
Unassigned
Components:
build-user-vars
Created:
02/Jun/14 11:44 AM
Description:
Precondition:
install rebuild plugin
create a Job A that triggers a Job B
Job A has a log rotation set to "keep 2 builds", Job B has no log rotation set
run Job A several times (let say 5 times)
Actual:
Job A - history: build 4 and build 5
Job B - history: build 1,2,3,4 and 5
Action:
Select Job B build 2 and run "rebuild" via "rebuild plugin"
Currently:
java.lang.NullPointerException
at org.jenkinsci.plugins.builduser.BuildUser.makeUserBuildVariables(BuildUser.java:73)
at org.jenkinsci.plugins.builduser.BuildUser.makeUserBuildVariables(BuildUser.java:77)
at org.jenkinsci.plugins.builduser.BuildUser.makeBuildVariables(BuildUser.java:64)
at hudson.model.AbstractBuild.getBuildVariables(AbstractBuild.java:984)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
Problem:
org.jenkinsci.plugins.builduser.BuildUser.makeUserBuildVariables(Run build, Map variables)
// If build has been triggered form an upstream build, get UserCause from there to set user build variables
Cause.UpstreamCause upstreamCause = (Cause.UpstreamCause) build.getCause(Cause.UpstreamCause.class);
if (upstreamCause != null) {
Job job = Jenkins.getInstance().getItemByFullName(upstreamCause.getUpstreamProject(), Job.class);
Run upstream = job.getBuildByNumber(upstreamCause.getUpstreamBuild());
makeUserBuildVariables(upstream, variables);
}
The problem is that the upstreamCause is checked for null, but in case of logrotation (or maybe also an manual delete) has deleted the upstream-run - the variable "upstream" is not checked to null. That leads to a recursive-call where method-argument "build" is null which is also not checked.
Suggestion:
either return on "build == null"
or check Run upstream = job.getBuildByNumber(upstreamCause.getUpstreamBuild()); for null too
Environment:
Plugin v1.3
Project:
Jenkins
Priority:
Major
Reporter:
Sven Appenrodt
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-user-vars] (JENKINS-23269) NPE when getting upstreambuild after starting a rebuild
Sven Appenrodt resolved JENKINS-23269 as Duplicate NPE when getting upstreambuild after starting a rebuild Duplicate to JENKINS-22974. Found this one too late - sry Change By: Sven Appenrodt (02/Jun/14 12:03 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23193) UI blocked frequently
K P commented on JENKINS-23193 UI blocked frequently Had similar issues in the past. Finally resolved by adding more heap space (if I remember well); just set the appropriate Java startup options in your jenkins.xml (and if it weren't the heap space options, it must have been the PermSize ones) So try increasing the memory. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvfb] (JENKINS-23267) NullPointerException in XvfbBuildWrapper.setUp when configured without node label restrictions
Jarosław Strzelecki commented on JENKINS-23267 NullPointerException in XvfbBuildWrapper.setUp when configured without node label restrictions Confirm. Introduced in 1.0.11. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23248) CLI: get-job calls are causing file descriptor leaks.
Craig Phillips updated JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. Here is a delta with approximately an hour between each snapshot. Change By: Craig Phillips (02/Jun/14 12:52 PM) Attachment: jkfd.txt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-parameter-summary] (JENKINS-23270) After migrating to another IP hyperlink in "Slaves in label" still refers to old value.
Kirill Bucharsky created JENKINS-23270 After migrating to another IP hyperlink in "Slaves in label" still refers to old value. Issue Type: Bug Affects Versions: current Assignee: Oliver Gondža Components: job-parameter-summary Created: 02/Jun/14 12:58 PM Description: So I have VM with Jenkins in production and I've cloned it to try some configuration. When I go to Job Configuration, check "Restrict where this project can be run", and fill in label, I'm getting following: "Slaves in label: 2". It's OK, but hyperlink in word "label" still contains fqdn of production VM. Since all other links were transformed by Jenkins from fqdn of production to IP of clone, this was unexpected. And this could result in failure in production because moving from clone to prod. was too easy and might be noticed only by looking into address bar. Honestly, I don't do it that often. Example: I've had "jenkins.example.org" and clone has "192.168.0.15". So I will have page with address "http://192.168.0.15/job/test/configure", with "Slaves in label" refers to "http://jenkins.example.org/label/label-test" instead of "http://192.168.0.15/label/label-test" Environment: Debian 7, Jenkins 1.565 Project: Jenkins Labels: configuration label Priority: Minor Reporter: Kirill Bucharsky This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-parameter-summary] (JENKINS-23270) After migrating to another IP hyperlink in "Slaves in label" still refers to old value.
Kirill Bucharsky updated JENKINS-23270 After migrating to another IP hyperlink in "Slaves in label" still refers to old value. Change By: Kirill Bucharsky (02/Jun/14 12:59 PM) Description: So I have VM with Jenkins in production and I've cloned it to try some configuration. When I go to Job Configuration on clone , check "Restrict where this project can be run", and fill in label, I'm getting following: "Slaves in label: 2". It's OK, but hyperlink in word "label" still contains fqdn of production VM. Since all other links were transformed by Jenkins from fqdn of production to IP of clone, this was unexpected. And this could result in failure in production because moving from clone to prod. was too easy and might be noticed only by looking into address bar. Honestly, I don't do it that often.Example:I've had "jenkins.example.org" and clone has "192.168.0.15".So I will have page with address "http://192.168.0.15/job/test/configure", with "Slaves in label" refers to "http://jenkins.example.org/label/label-test" instead of "http://192.168.0.15/label/label-test" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23270) After migrating to another IP hyperlink in "Slaves in label" still refers to old value.
Oliver Gondža updated JENKINS-23270 After migrating to another IP hyperlink in "Slaves in label" still refers to old value. Change By: Oliver Gondža (02/Jun/14 1:09 PM) Assignee: Oliver Gondža Component/s: core Component/s: job-parameter-summary This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23270) After migrating to another IP hyperlink in "Slaves in label" still refers to old value.
Oliver Gondža commented on JENKINS-23270 After migrating to another IP hyperlink in "Slaves in label" still refers to old value. I assumed you have cloned the global configuration without changing Jenkins URL in global config. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23270) After migrating to another IP hyperlink in "Slaves in label" still refers to old value.
Kirill Bucharsky commented on JENKINS-23270 After migrating to another IP hyperlink in "Slaves in label" still refers to old value. Yes, you're right. But look: I started new VM, Jenkins, logged in and saw all links now pointing to new VM IP. I thought it is all right. And then, suddenly, one link depends on system variable. I think, either all of them should depend on Jenkins URL, or no one. Or am I missing some logic in this exact behavior? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [s3] (JENKINS-19725) Unable to unmarshall response (Couldn't initialize a SAX driver to create an XMLReader)
Julio Gonzalez Gil commented on JENKINS-19725 Unable to unmarshall response (Couldn't initialize a SAX driver to create an XMLReader) Same here with Jenkins 1.558 and S3 plugin 0.6. The credentials are working fine with s3cmd. Jun 02, 2014 3:31:32 PM hudson.plugins.s3.S3BucketPublisher$DescriptorImpl doLoginCheck SEVERE: Unable to unmarshall response (Couldn't initialize a SAX driver to create an XMLReader). Response Code: 200, Response Text: OK com.amazonaws.AmazonClientException: Unable to unmarshall response (Couldn't initialize a SAX driver to create an XMLReader). Response Code: 200, Response Text: OK at com.amazonaws.http.AmazonHttpClient.handleResponse(AmazonHttpClient.java:739) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:400) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:233) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3569) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3522) at com.amazonaws.services.s3.AmazonS3Client.listBuckets(AmazonS3Client.java:669) at com.amazonaws.services.s3.AmazonS3Client.listBuckets(AmazonS3Client.java:677) at hudson.plugins.s3.S3Profile.check(S3Profile.java:113) at hudson.plugins.s3.S3BucketPublisher$DescriptorImpl.doLoginCheck(S3BucketPublisher.java:294) at sun.reflect.GeneratedMethodAccessor489.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.Chai
[JIRA] [crowd2] (JENKINS-11912) SSO not working
Martin Alig commented on JENKINS-11912 SSO not working Hey, I have exactly the same issue here. How did you solve this problem? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-23165) Config.gerritAuthKeyFilePassword stored in plaintext
SCM/JIRA link daemon commented on JENKINS-23165 Config.gerritAuthKeyFilePassword stored in plaintext Code changed in jenkins User: rinrinne Path: src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/config/Config.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/config/IGerritHudsonTriggerConfig.java src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritServer/index.jelly src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/config/ConfigTest.java src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/mock/MockGerritHudsonTriggerConfig.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/d402536e48c300aa435c3f3e519e7754fc769ecf Log: Prevent to send plaintext password to browser Fix for JENKINS-23165 and pull #157 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-20384) Please improve triggers UI
SCM/JIRA link daemon commented on JENKINS-20384 Please improve triggers UI Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/AttachmentUtils.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherContext.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java src/main/java/hudson/plugins/emailext/plugins/ContentBuilder.java src/main/java/hudson/plugins/emailext/plugins/trigger/RegressionTrigger.java src/main/resources/hudson/plugins/emailext/plugins/trigger/AbortedTrigger/help.html src/main/resources/hudson/plugins/emailext/plugins/trigger/AlwaysTrigger/help.html src/main/resources/hudson/plugins/emailext/plugins/trigger/ImprovementTrigger/help.html src/main/resources/hudson/plugins/emailext/plugins/trigger/PreBuildScriptTrigger/help.html src/main/resources/hudson/plugins/emailext/plugins/trigger/PreBuildTrigger/help.html src/main/resources/hudson/plugins/emailext/plugins/trigger/RegressionTrigger/help.html src/main/resources/hudson/plugins/emailext/plugins/trigger/ScriptTrigger/help.html src/main/resources/hudson/plugins/emailext/plugins/trigger/StillUnstableTrigger/help.html src/main/resources/hudson/plugins/emailext/plugins/trigger/UnstableTrigger/help.html src/test/java/hudson/plugins/emailext/plugins/ContentBuilderTest.java http://jenkins-ci.org/commit/email-ext-plugin/7980566ba93d24b4efd8dcbaddfb52bb5e9a83b5 Log: Fix JENKINS-20384 Added more information to the help files. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase] (JENKINS-23271) Intermittent Ivalid Object ID in remoting module
Paul Becotte created JENKINS-23271 Intermittent Ivalid Object ID in remoting module Issue Type: Bug Assignee: Vincent Latombe Components: clearcase, core Created: 02/Jun/14 2:29 PM Description: For the last two weeks, I have been seeing an intermittent failure during the clearcase stage of our builds. It throws a Java exception along the lines of FATAL: Invalid object ID 18649 iuota=18470 java.lang.IllegalStateException: Invalid object ID 18469 iota=18470 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:277) etc... It always happens during the Clearcase segment of the build, but on a different step each time. Sometimes after lsview, sometimes after lshistory, sometimes after mkview ... It happens a very low percentage of the time, and it happens on a different project each time. I have around 300 projects running between a number of matrix jobs- we are seeing one or two failures on each runthrough of this, always on different jobs and on different slaves. It started a couple weeks ago- our clearcase server crashed, and jenkins was having some trouble interacting with the server. I upgraded to 1.563 to try and solve that problem (I wound up having to manually delete all the views that had been created in the period between the backup and the crash). Once that issue had been resolved though, we started seeing this problem. I upgraded the clearcase plugin to 1.5, and then tried downgrading Jenkins to 1.554.2. I cannot swear to it, but I thought I was on 1.558 before the first problem popped up, and had been very stable for a long time with all build failures being attributed to bad code, so suddenly having Jenkins fail some is kind of jarring. At this point, I am not sure what I changed to cause the problem. I remember I had to upgrade slave.jar to version 2.41 from whatever it was before when I did the first upgrade to 1.563. Other then that, nothing else substantial has changed. The Jenkins is on a restricted network with no internet access- I am going to type the stack trace below, so forgive any typos. FATAL: Invalid object ID 18649 iuota=18470 java.lang.IllegalStateException: Invalid object ID 18469 iota=18470 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:277) at hudson.remoting.ExportTable.get(ExportTable.java:261) at hudson.remoting.Channel.getExportedObject(Channel.java:596) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:292 at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:281) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:240) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(UNKNOWN SOURCE) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) Cased by: java.lang.Exception: Object was recently deallocated #18649 (ref.0) : hudson.Launcher$RemoteLaunchCallable$1 created at Fri May 30 19:27:39 EDT 2014 at hudson.remoting.ExportTable$Entry.(ExportTable.java:86) at hudson.remoting.ExportTable.export(ExportTable.java:239) at hudson.remoting.Channel.export(Channel.java:592) at hudson.remoting.Channel.export(Channel.java:583) at hudson.remoting.Channel.export(Channel.java:553) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1025) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:990) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at
[JIRA] [email-ext] (JENKINS-22041) email-ext - new failed test regression trigger
SCM/JIRA link daemon commented on JENKINS-22041 email-ext - new failed test regression trigger Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/plugins/trigger/RegressionTrigger.java http://jenkins-ci.org/commit/email-ext-plugin/de6ee279a67091fb58405193c9d9acc3a5e3ac89 Log: Fix JENKINS-22041 Added check to see if any tests failed this time that didn't fail last time This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-17756) The jenkins repository is in the jenkins RPM
Ralph Bolton commented on JENKINS-17756 The jenkins repository is in the jenkins RPM FWIW, I agree too. I'm install Jenkins on a closed network, so the repo file is entirely useless, and actually breaks 'yum' because it's unable to connect to the Jenkins repo server. I've solved the problem by installing Jenkins with Puppet and having it alter the repo file to put 'enabled=0' into it. For cases where Jenkins isn't installed with Puppet, I've put some post-install into a few other commonly used packages to do the same thing. All should be unneccessary - splitting the RPM would be a great help. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-15883) Allow to automatically trigger jobs when a project import the dependencyManagement of another
Yvan Girard commented on JENKINS-15883 Allow to automatically trigger jobs when a project import the dependencyManagement of another We are in process to modify all our maven projects to use DependencyManagement and imported BOM. We are also using Jenkins and we have issue the same issue as described in JENKINS-15883 (ref https://issues.jenkins-ci.org/browse/JENKINS-15883). There is any development on this or a 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] [core] (JENKINS-17756) The jenkins repository is in the jenkins RPM
Ralph Bolton edited a comment on JENKINS-17756 The jenkins repository is in the jenkins RPM FWIW, I agree too. I'm install Jenkins on a closed network, so the repo file is entirely useless, and actually breaks 'yum' because it's unable to connect to the Jenkins repo server. I've solved the problem by installing Jenkins with Puppet and having it alter the repo file to put 'enabled=0' into it. For cases where Jenkins isn't installed with Puppet, I've put some post-install into a few other commonly used packages to do the same thing. All should be unneccessary - splitting the RPM would be a great help. Update: Looks like this is fixed: https://issues.jenkins-ci.org/browse/JENKINS-22690 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23273) RPM post-install should not do a "chown -R jenkins:jenkins /var/lib/jenkins"
Ralph Bolton
created JENKINS-23273
RPM post-install should not do a "chown -R jenkins:jenkins /var/lib/jenkins"
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
02/Jun/14 2:46 PM
Description:
The jenkins-1.565-1.1 RPM contains a post-install script with performs the following:
Ensure the right ownership on files
. /etc/sysconfig/jenkins
chown -R ${JENKINS_USER:-jenkins} /var/log/jenkins
chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}
These chowns can take a very long time on systems with lots of files. A couple of our Jenkins boxes have thousands of files in a the /var/lib/jenkins/workspace directory (which itself is a network mount), which means this chown takes many minutes to complete (like ~15 minutes). This holds up package deployment unnecessarily.
I propose that either these chowns be removed entirely (the RPM spec sets the ownership of things the RPM puts down), or better yet that they're restricted to specific files.
Project:
Jenkins
Labels:
yum
rpm
Priority:
Major
Reporter:
Ralph Bolton
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-23272) java.io.IOException: remote file operation failed remote slave Unable to delete
Khaled Janania created JENKINS-23272 java.io.IOException: remote file operation failed remote slave Unable to delete Issue Type: Bug Assignee: Unassigned Components: core Created: 02/Jun/14 2:45 PM Description: Received this exception when I tried to wipe the workspace of a remote slave: java.io.IOException: remote file operation failed: /home/gos-ops/jenkins/workspace/Build-GOS-SyncPackages/build on slaves and master/slave_ams01 at hudson.remoting.Channel@558965d7:slave_ams01 at hudson.FilePath.act(FilePath.java:916) at hudson.FilePath.act(FilePath.java:893) at hudson.FilePath.deleteRecursive(FilePath.java:1082) at hudson.model.AbstractProject.doDoWipeOutWorkspace(AbstractProject.java:1895) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:89) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.Chained
[JIRA] [core] (JENKINS-23272) java.io.IOException: remote file operation failed remote slave Unable to delete
Khaled Janania updated JENKINS-23272 java.io.IOException: remote file operation failed remote slave Unable to delete Change By: Khaled Janania (02/Jun/14 2:51 PM) Environment: Linux 2.6.18-348. 16 12 .1.el5Red Hat Enterprise Linux Server release 5.9 (Tikanga) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23273) RPM post-install should not do a "chown -R jenkins:jenkins /var/lib/jenkins"
Ralph Bolton
updated JENKINS-23273
RPM post-install should not do a "chown -R jenkins:jenkins /var/lib/jenkins"
Change By:
Ralph Bolton
(02/Jun/14 2:51 PM)
Description:
The jenkins-1.565-1.1 RPM contains a post-install script with performs the following:
{quote}{noformat}
# Ensure the right ownership on files. /etc/sysconfig/jenkinschown -R ${JENKINS_USER:-jenkins} /var/log/jenkinschown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}
{noformat}{quote}
These chowns can take a very long time on systems with lots of files. A couple of our Jenkins boxes have thousands of files in a the /var/lib/jenkins/workspace directory (which itself is a network mount), which means this chown takes many minutes to complete (like ~15 minutes)
and actually changes the ownership of no files
. This holds up package deployment unnecessarily.I propose that either these chowns be removed entirely (the RPM spec sets the ownership of things the RPM puts down), or better yet that they're restricted to specific files.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-23272) java.io.IOException: remote file operation failed remote slave Unable to delete
Khaled Janania commented on JENKINS-23272 java.io.IOException: remote file operation failed remote slave Unable to delete Could it be related to the directory depth? The depth can go somewhat deep since we use it to sync a lot of packages and versions of packages. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvfb] (JENKINS-23267) NullPointerException in XvfbBuildWrapper.setUp when configured without node label restrictions
elygre
commented on JENKINS-23267
NullPointerException in XvfbBuildWrapper.setUp when configured without node label restrictions
The required code should use "&&", but it also must negate the isEmpty() (to get those that are not empty):
if (assignedLabels != null && !assignedLabels.trim().isEmpty()) {
// Do something using the label
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-6545) JUnit report parsing cannot handle nested suites
Andrei Costescu commented on JENKINS-6545 JUnit report parsing cannot handle nested suites I've been searching for a while for a tool that would generate this kind of nested report for JUnit. Did any of you actually have such a nested report xml generated from nested JUnit tests suites (either 3.x or 4.x)? Or it it only generated by other testing frameworks? For example ant xml formatter flattens test suites, doesn't keep nesting. Maven surefire does the same. Even tried TestNG wrapped around JUnit with the same result. (junit 4.11 (used 3 like style and 4 like style), testNG 6.8, ant 1.9.4, maven-surefire-plugin 2.17) So which is the test runner that would generate such a nested report for a nested JUnit suite? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-6545) JUnit report parsing cannot handle nested suites
Andrei Costescu edited a comment on JENKINS-6545 JUnit report parsing cannot handle nested suites Actually I found one but not very useful for Jenkins (the eclipse jUnit results view has an Export in a menu that will generate such xml). So I need on that can be used in Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-6545) JUnit report parsing cannot handle nested suites
Andrei Costescu edited a comment on JENKINS-6545 JUnit report parsing cannot handle nested suites Actually I found one but not very useful for Jenkins (the eclipse jUnit results view has an Export in a menu that will generate such xml). So I need one that can be used in Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-6545) JUnit report parsing cannot handle nested suites
Andrei Costescu commented on JENKINS-6545 JUnit report parsing cannot handle nested suites Actually I found one but not very useful for Jenkins (the eclipse jUnit results view has an Export in a menu that will generate such xml). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23272) java.io.IOException: remote file operation failed remote slave Unable to delete
Khaled Janania updated JENKINS-23272 java.io.IOException: remote file operation failed remote slave Unable to delete Change By: Khaled Janania (02/Jun/14 2:54 PM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2] (JENKINS-11912) SSO not working
Kanstantsin Shautsou commented on JENKINS-11912 SSO not working Add jenkins.security, hudson.security, de.theit.jenkins.crowd to logger. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout
Kevin Cross commented on JENKINS-23146 StringIndexOutOfBoundsException on subversion checkout I am not sure I can test this. I decided to stick with version 2.4 but I have not seen this problem since. This seems odd as I did see the issue a number of times in the day or two after my last upgrade but not since. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23271) Intermittent Ivalid Object ID in remoting module
Vincent Latombe updated JENKINS-23271 Intermittent Ivalid Object ID in remoting module Change By: Vincent Latombe (02/Jun/14 3:27 PM) Component/s: clearcase This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23271) Intermittent Ivalid Object ID in remoting module
Vincent Latombe commented on JENKINS-23271 Intermittent Ivalid Object ID in remoting module This is unrelated to clearcase plugin, it seems only related to remoting layer. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23271) Intermittent Ivalid Object ID in remoting module
Paul Becotte commented on JENKINS-23271 Intermittent Ivalid Object ID in remoting module That is fine- I wasn't sure and figured it would be better for someone who was sure to make the call. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-11912) SSO not working
Martin Alig commented on JENKINS-11912 SSO not working Thanks for the quick response. Here some snippet from the logs: Jun 02, 2014 5:34:16 PM FINER hudson.security.SidACL hasPermission(PrincipalSID:anonymous,Permission[class hudson.model.Hudson,Read])=>true Jun 02, 2014 5:34:16 PM FINE hudson.security.SidACL hasPermission(org.acegisecurity.providers.anonymous.AnonymousAuthenticationToken@7ceb1ed7: Username: anonymous; Password: [PROTECTED]; Authenticated: true; Details: org.acegisecurity.ui.WebAuthenticationDetails@957e: RemoteIpAddress: 192.168.188.102; SessionId: null; Granted Authorities: ,Permission[class hudson.model.Hudson,Read])=>true Jun 02, 2014 5:34:17 PM FINER hudson.security.SidACL hasPermission(PrincipalSID:anonymous,Permission[class hudson.model.Hudson,Administer])=>true Jun 02, 2014 5:34:17 PM FINE hudson.security.SidACL hasPermission(org.acegisecurity.providers.anonymous.AnonymousAuthenticationToken@7ceb1ed7: Username: anonymous; Password: [PROTECTED]; Authenticated: true; Details: org.acegisecurity.ui.WebAuthenticationDetails@957e: RemoteIpAddress: 192.168.188.102; SessionId: null; Granted Authorities: ,Permission[class hudson.model.Hudson,Administer])=>true Jun 02, 2014 5:34:17 PM FINER hudson.security.SidACL hasPermission(PrincipalSID:anonymous,Permission[class hudson.model.Hudson,Read])=>true Jun 02, 2014 5:34:17 PM FINE hudson.security.SidACL hasPermission(org.acegisecurity.providers.anonymous.AnonymousAuthenticationToken@7ceb1ed7: Username: anonymous; Password: [PROTECTED]; Authenticated: true; Details: org.acegisecurity.ui.WebAuthenticationDetails@957e: RemoteIpAddress: 192.168.188.102; SessionId: null; Granted Authorities: ,Permission[class hudson.model.Hudson,Read])=>true Jun 02, 2014 5:34:17 PM FINER jenkins.security.ExceptionTranslationFilter Chain processed normally Jun 02, 2014 5:34:18 PM FINER hudson.security.HudsonFilter doFilter ENTRY Jun 02, 2014 5:34:18 PM FINE de.theit.jenkins.crowd.CrowdServletFilter User is not logged in (anymore) via Crowd => logout user Jun 02, 2014 5:34:18 PM FINE de.theit.jenkins.crowd.CrowdRememberMeServices Logout user and close SSO session Jun 02, 2014 5:34:18 PM FINER hudson.security.HudsonFilter doFilter ENTRY Jun 02, 2014 5:34:18 PM FINE de.theit.jenkins.crowd.CrowdServletFilter User is not logged in (anymore) via Crowd => logout user Jun 02, 2014 5:34:18 PM FINE de.theit.jenkins.crowd.CrowdRememberMeServices Logout user and close SSO session Jun 02, 2014 5:34:18 PM FINER hudson.security.HudsonFilter doFilter ENTRY Jun 02, 2014 5:34:18 PM FINE de.theit.jenkins.crowd.CrowdServletFilter User is not logged in (anymore) via Crowd => logout user Jun 02, 2014 5:34:18 PM FINE de.theit.jenkins.crowd.CrowdRememberMeServices Logout user and close SSO session Jun 02, 2014 5:34:18 PM FINER hudson.security.HudsonFilter doFilter ENTRY Jun 02, 2014 5:34:18 PM FINE de.theit.jenkins.crowd.CrowdServletFilter User is not logged in (anymore) via Crowd => logout user Jun 02, 2014 5:34:18 PM FINE de.theit.jenkins.crowd.CrowdRememberMeServices Logout user and close SSO session Jun 02, 2014 5:34:18 PM FINER hudson.security.HudsonFilter doFilter ENTRY Jun 02, 2014 5:34:18 PM FINE de.theit.jenkins.crowd.CrowdServletFilter User is not logged in (anymore) via Crowd => logout user Jun 02, 2014 5:34:18 PM FINE de.theit.jenkins.crowd.CrowdRememberMeServices Logout user and close SSO session Jun 02, 2014 5:34:18 PM FINER hudson.security.HudsonFilter doFilter ENTRY Jun 02, 2014 5:34:18 PM FINE de.theit.jenkins.crowd.CrowdServletFilter User is not logged in (anymore) via Crowd => logout user Jun 02, 2014 5:34:18 PM FINE de.theit.jenkins.crowd.CrowdRememberMeServices Logout user and close SSO session Jun 02, 2014 5:34:18 PM FINER hudson.security.ChainedServletFilter doFilter ENTRY Jun 02, 2014 5:34:18 PM FINER de.theit.jenkins.crowd.CrowdRememberMeServices Checking whether a SSO token is available... Jun 02, 2014 5:34:18 PM FINER jenkins.security.ExceptionTranslationFilter Chain processed normally Jun 02, 2014 5:34:18 PM FINER hudson.security.HudsonFilter doFilter ENTRY Jun 02, 2014 5:34:18 PM FINE de.theit.jenkins.crowd.CrowdServletFilter User is not logged in (anymore) via Crowd => logout user Jun 02, 2014 5:34:18 PM FINE de.theit.jenkins.crowd.CrowdRememberMeServices Logout user and close SSO session Jun 02, 2014 5:34:18 PM FINER hudson.security.ChainedServletFilter doFilter ENTRY
[JIRA] [core] (JENKINS-12229) Loading Overlay does not go away - FF8
centic commented on JENKINS-12229 Loading Overlay does not go away - FF8 I didn't see this any more since a few months, so from my side this is fixed or at least does not occur any more. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-11912) SSO not working
Martin Alig commented on JENKINS-11912 SSO not working What is strange, that the oppsite way works. So logging in into Jenkins and then the SSO works for all the other configured applications... Could it have something to the with my Apache Proxy Setting? Basically how I have it configure is: Public Host: Apache Proxy Crowd (Behind Apache) ... Internal Host: Jenkins And in the Public Host I have the ProxyPass configured like: ProxyPass /jenkins http://192.168.178.22:8080/jenkins nocanon ProxyPassReverse /jenkins http://192.168.178.22:8080/jenkins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-23274) Do not output the "Evaluated Groovy script" to console
Marc Günther updated JENKINS-23274 Do not output the "Evaluated Groovy script" to console Change By: Marc Günther (02/Jun/14 4:04 PM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-23274) Do not output the "Evaluated Groovy script" to console
Marc Günther created JENKINS-23274 Do not output the "Evaluated Groovy script" to console Issue Type: Bug Assignee: Gregory Boissinot Components: envinject Created: 02/Jun/14 4:03 PM Description: The contents of the "Evaluated Groovy script" are printed to the Console of every build. This only clutters the Console output and is very confusing for our users. Can it be disabled? Project: Jenkins Priority: Trivial Reporter: Marc Günther This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-11912) SSO not working
Kanstantsin Shautsou reopened JENKINS-11912 SSO not working Change By: Kanstantsin Shautsou (02/Jun/14 4:04 PM) Resolution: Not A Defect Status: Closed Reopened Assignee: Thorsten Heit Kanstantsin Shautsou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-11912) SSO not working
Kanstantsin Shautsou commented on JENKINS-11912 SSO not working Plus add com.atlassian.crowd to logger Filter routine tries to extract token, here it fails. Check that SSO domain configured right plus check errors from com.atlassian.crowd library. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-19074) Why "More than 1 builds are needed for the trend report"?
Marc Günther commented on JENKINS-19074 Why "More than 1 builds are needed for the trend report"? What about consistency? I always click on the "trend" link, when I want to see the build times. There is absolutely no reason whatsoever to not display it. The fact that the information is displayed somewhere else is besides the point. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-17471) Maven Buildstep and Maven project are completely different
Marc Günther commented on JENKINS-17471 Maven Buildstep and Maven project are completely different Having two completely independent implementations for doing the same thing does not really sound like a good design decision to me This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2] (JENKINS-11912) SSO not working
Kanstantsin Shautsou edited a comment on JENKINS-11912 SSO not working Plus add com.atlassian.crowd to logger Filter routine checks auth at https://github.com/jenkinsci/crowd2-plugin/blob/master/src/main/java/de/theit/jenkins/crowd/CrowdServletFilter.java#L139 Check that SSO domain configured right plus check errors from com.atlassian.crowd library. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23270) After migrating to another IP hyperlink in "Slaves in label" still refers to old value.
Oliver Gondža commented on JENKINS-23270 After migrating to another IP hyperlink in "Slaves in label" still refers to old value. Or am I missing some logic in this exact behavior? No, the link should be corrected. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-18869) list-view with lots of tabs renders a very wide job table
Marc Günther commented on JENKINS-18869 list-view with lots of tabs renders a very wide job table I just tried this on Safari, Chrome and Firefox (all MacOSX). When I have a page with for example >30 tabs that don't fit horizontally inside the window anymore, then the table with the list of jobs below it also gets expanded to fit the entire width of the page. What I would expect is that the table takes only as much horizontal space as it needs to display everything without wrapping, and not grow to fit the entire tab bar above 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] [core] (JENKINS-21930) Jobs fail due to "node went offline during the build"
Marc Günther commented on JENKINS-21930 Jobs fail due to "node went offline during the build" We have mostly Swarm slaves, and I usually use the jenkins-cli offline-node command, although I might have used the "Mart this node temporarily offline" button once in a while. I am not sure if it also happens on ssh slaves. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22490) weather icon also for test failures, not only build failures
Marc Günther commented on JENKINS-22490 weather icon also for test failures, not only build failures Not really a helpful behaviour, as usually we have maybe a couple of failing unit tests, but definitely never >20%. How could that even happen? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-23275) ScmSyncConfiguration NullPointerException on postCredential
Sami Tuohino created JENKINS-23275 ScmSyncConfiguration NullPointerException on postCredential Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 02/Jun/14 4:42 PM Description: Hi, I didn't see any open issues about this, lots of previous and supposedly resolved discussions though Jenkins ver. 1.565 SCM Sync Configuration Plugin: 0.0.7.4 Credentials Plugin: 1.13 Subversion Plug-in: 2.4 http://localhost:8080/scm/SubversionSCM/postCredential Stack trace javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.
[JIRA] [plugin] (JENKINS-17480) Copying a job should disable the copy while editing it
Marc Günther commented on JENKINS-17480 Copying a job should disable the copy while editing it Why a plugin? "Copy existing job" is a core functionality, and should do the right thing. The current behaviour is simply broken. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-21930) Jobs fail due to "node went offline during the build"
Daniel Beck commented on JENKINS-21930 Jobs fail due to "node went offline during the build" Both are the same feature, marking a node offline rather than disconnecting. This is not supposed to cut any connections. Is this reproducible on a pristine Jenkins instance, no plugins etc.? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-18534) Cannot add new build to queue from same project with different parameters
Shannon Kerr updated JENKINS-18534 Cannot add new build to queue from same project with different parameters Change By: Shannon Kerr (02/Jun/14 4:50 PM) 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] [core] (JENKINS-18869) list-view with lots of tabs renders a very wide job table
Daniel Beck commented on JENKINS-18869 list-view with lots of tabs renders a very wide job table To clarify, I meant I don't expect this to be changed. I don't doubt that this is the behavior you're seeing. That being said, this might have an easy solution once Jenkins switches to a layout that isn't table-based, something currently being discussed on the developers' mailing list. Before that, I doubt it. Still, my recommendation stands to just use a different kind of tab bar. Alternatively, you might be able to use the Simple Theme plugin and a few lines of JS/CSS to rotate the text 90 degrees, so the tabs take less horizontal space. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18534) Cannot add new build to queue from same project with different parameters
Shannon Kerr commented on JENKINS-18534 Cannot add new build to queue from same project with different parameters Can anything be done about this issue? I have to have developers enter some unique test to prevent their jobs from being combined. I'd really like to hear about a fix for this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22490) weather icon also for test failures, not only build failures
Daniel Beck commented on JENKINS-22490 weather icon also for test failures, not only build failures 5 tests, 1 failing? Seriously though, that's how the regular weather icons work (see the file names!). What plugin are you using for the tests? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-17471) Maven Buildstep and Maven project are completely different
Daniel Beck commented on JENKINS-17471 Maven Buildstep and Maven project are completely different It's not the same thing. One is a special, magical job type that hooks into the Maven process to be able to not require configuration and do lots of automatic magic. Requires special support in Jenkins for every major(ish) Maven release, and is difficult to debug according to Stephen Connolly: http://javaadventure.blogspot.de/2013/11/jenkins-maven-job-type-considered-evil.html The other is a nicer interface to the Maven command line call that just provides the Maven installation automatically if so configured. Both are included out of the box probably more for historical reasons than anything else. Jenkins tries hard to not break backwards compatibility. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-18869) list-view with lots of tabs renders a very wide job table
Marc Günther commented on JENKINS-18869 list-view with lots of tabs renders a very wide job table Ah, lol, now I understand We are currently using Nested Views plugin and have a couple of views where this is happening. I might try the DropDown ViewsTabBar you mentioned. 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] [xvfb] (JENKINS-23267) NullPointerException in XvfbBuildWrapper.setUp when configured without node label restrictions
SCM/JIRA link daemon commented on JENKINS-23267 NullPointerException in XvfbBuildWrapper.setUp when configured without node label restrictions Code changed in jenkins User: Zoran Regvart Path: src/main/java/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper.java http://jenkins-ci.org/commit/xvfb-plugin/b6573ff15938ea035fd9d9b29bb13cfd16d16367 Log: JENKINS-23267 NullPointerException in XvfbBuildWrapper.setUp when configured without node label restrictions This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-17480) Copying a job should disable the copy while editing it
Oleg Nenashev commented on JENKINS-17480 Copying a job should disable the copy while editing it Plugin allows to propagate changes to all newest Jenkins versions (including LTS releases). Such approach also allows to maintain the feature set independently of the core. Since Jenkins provides all required extension points, there's no need to implement the feature within the 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] [xvfb] (JENKINS-23267) NullPointerException in XvfbBuildWrapper.setUp when configured without node label restrictions
zregvart resolved JENKINS-23267 as Fixed NullPointerException in XvfbBuildWrapper.setUp when configured without node label restrictions This slipped in 1.0.11, sorry about that. Thanks for reporting and suggesting the fix. Version 1.0.12 is released that fixes this and should be available soon on the update center. Change By: zregvart (02/Jun/14 5:11 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] [core] (JENKINS-19385) IOException while archiving a file from remote workspace
robsimon commented on JENKINS-19385 IOException while archiving a file from remote workspace could this message come from "abort if stuck - absolute"? I saw a few jobs dying over the weekend but the logs are already rotated away. I removed the "abort if stuck" option. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvfb] (JENKINS-23155) Only run plugin under Linux
zregvart closed JENKINS-23155 as Fixed Only run plugin under Linux Change By: zregvart (02/Jun/14 5:12 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22490) weather icon also for test failures, not only build failures
Marc Günther commented on JENKINS-22490 weather icon also for test failures, not only build failures We have more like >8000 tests. 20% is definitely not going to happen Yea, I know how the weather icon works, I was merely questioning its usefulness in this particular case. As for plugins, nothing special, just the normal "Publish junit test result" thingy. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-17480) Copying a job should disable the copy while editing it
Marc Günther commented on JENKINS-17480 Copying a job should disable the copy while editing it I would still maintain that this is a bug in the existing implementation, and not a feature. And as such it doesn't belong into a 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] [disk-usage] (JENKINS-22753) Disk Usage graph doesn't display on project pages
Walter Kacynski commented on JENKINS-22753 Disk Usage graph doesn't display on project pages Are you using Folders as part of your job configuration? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage] (JENKINS-19070) Disk usage doesn't work - 1.523+
Walter Kacynski resolved JENKINS-19070 as Incomplete Disk usage doesn't work - 1.523+ Change By: Walter Kacynski (02/Jun/14 5:23 PM) Status: Open Resolved Assignee: Lucie Votypkova Magnus Fromreide Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
