[JIRA] [copyartifact] (JENKINS-24892) Copyartifact 2.0
ikedam created JENKINS-24892 Copyartifact 2.0 Issue Type: New Feature Assignee: ikedam Components: copyartifact Created: 27/Sep/14 6:14 AM Description: I plan to start to develop Copyartifact 2.0 with major changes which may no longer preserve compatibility from 1.X. Project: Jenkins Priority: Major Reporter: ikedam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-24891) Remove FilePathCopyMethod from copyartifact
ikedam created JENKINS-24891 Remove FilePathCopyMethod from copyartifact Issue Type: New Feature Assignee: Unassigned Components: copyartifact Created: 27/Sep/14 6:13 AM Description: Copyartifact provides an extension point Copier which is to implement file copying operations. But it doesn't provide an interface to switch them, and it's only confusing to developers. Especially, FilePathCopyMethod, an old implementation for Copier is no longer used, and not tested at all. We should remove that. Project: Jenkins Priority: Minor Reporter: ikedam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-24890) BuildFilter-based configuration for Copyartifact
ikedam created JENKINS-24890 BuildFilter-based configuration for Copyartifact Issue Type: New Feature Assignee: Unassigned Components: copyartifact Created: 27/Sep/14 6:11 AM Description: Copyartifact provides BuildSelector and BuildFilter as mechanisms to select a build to copy from. But it mainly uses only BuildSelector. BuildFilter-based configuration would allow more flexible build specifications such as: the last completed build that is unstable or more AND a downstream of build XXX AND its parameter FOO is BAR or BAZ. Project: Jenkins Priority: Major Reporter: ikedam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-24889) Copyartifact should output more verbose messages
ikedam created JENKINS-24889 Copyartifact should output more verbose messages Issue Type: Improvement Assignee: Unassigned Components: copyartifact Created: 27/Sep/14 6:09 AM Description: Add an option to have outputs like "build XXX is skipped for unstable". There are often JIRA issues "the build wasn't properly selected", but there's no way to diagnose that. Project: Jenkins Priority: Major Reporter: ikedam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-24888) Complete runtime permission check of Copyartifact
ikedam created JENKINS-24888 Complete runtime permission check of Copyartifact Issue Type: Improvement Assignee: Unassigned Components: copyartifact Created: 27/Sep/14 6:07 AM Description: Copyartifact performs permission checks only when projects to copy from are specified with variables: See https://wiki.jenkins-ci.org/display/JENKINS/Copy+Artifact+Plugin#CopyArtifactPlugin-Permissionstocopyartifact This is misleading, users are often confused and that results in many JIRA issues. As the latest Jenkins provides a more flexible authorization model (QueueItemAuthenticator), it's time for copyartifact to check permissions even for projects specified without variables. Project: Jenkins Priority: Major Reporter: ikedam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-24887) Workflow support of Copyartifact
ikedam
created JENKINS-24887
Workflow support of Copyartifact
Issue Type:
Improvement
Assignee:
Unassigned
Components:
copyartifact
Created:
27/Sep/14 6:01 AM
Description:
With supporting SimpleBuildStep introduced in Jenkins 1.577...
(copied from https://github.com/jenkinsci/copyartifact-plugin/pull/43)
Atm, it works using the base 'step' step (i.e. you need to specify the $class) e.g.
node('master') {
// Do stuff
step($class: 'hudson.plugins.copyartifact.CopyArtifact', projectName: 'project1', filter: 'hellothere.txt')
// More stuff
}
Once the workflow apis are published we can build a dedicated step for this, it would look something like the following:
node('master') {
// Do stuff
copy(projectName: 'project1', filter: 'hellothere.txt')
// More stuff
}
Project:
Jenkins
Priority:
Major
Reporter:
ikedam
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-22637) "Copy Artifacts Plugin" should support ArtifactManager
ikedam commented on JENKINS-22637 "Copy Artifacts Plugin" should support ArtifactManager JENKINS-17494 can be also resolved by: Copyartifact supports ArtifactManager ArtifactDeploer provides ArtifactManager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-22637) "Copy Artifacts Plugin" should support ArtifactManager
ikedam
updated JENKINS-22637
"Copy Artifacts Plugin" should support ArtifactManager
Change By:
ikedam
(27/Sep/14 5:54 AM)
Summary:
Cannot use
"Copy Artifacts Plugin"
in conjuction with the "Compress Artifacts Plugin", archive not found.
should support ArtifactManager
Environment:
Windows 2012
Description:
ArtifactManager introduced in Jenkins 1.532 allows copyartifactto work with other plugins, such as [Compress Artifacts Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Compress+Artifacts+Plugin]
When using the [Compress Artifacts Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Compress+Artifacts+Plugin], the [Copy Artifact Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Copy+Artifact+Plugin] cannot find the zip archive created and fails when trying to copy the previous job's artifacts.The error is:{{Unable to access upstream artifacts area C:\JenkinsData\\builds\2014-04-15_17-02-29\archive. Does source project archive artifacts?}}The archive file is (no archive folder):{{C:\JenkinsData\\builds\2014-04-15_17-02-29\archive.zip}}
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] [copyartifact] (JENKINS-24886) Copyartifact Fallback Build Selector
ikedam created JENKINS-24886 Copyartifact Fallback Build Selector Issue Type: New Feature Assignee: ikedam Components: copyartifact Created: 27/Sep/14 5:09 AM Description: Specifies a sequence of build selectors build selector1, build selector2,... If build selector1 fails, tries build selector2. If build selector2 fails, tries build selector3. This is a generalized feature of fallbackToLastSuccessful of TriggeredBuildSelector. This would be powerful, and also resolves JENKINS-16108. Project: Jenkins Priority: Major Reporter: ikedam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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-24883) Artifacts not found on re-runs of manual jobs in pipeline
ikedam
updated JENKINS-24883
Artifacts not found on re-runs of manual jobs in pipeline
That's an issue of build-pipeline plugin.
Changed the component.
It sounds that build-pipeline doesn't set "upstream cause" of the rerun of Project C.
Attaching build.xml of the first run and the rerun of project C may help. They are located at ${JENKINS_HOME}/jobs/(name of Project C)/(build id)/build.xml.
Rebuild Plugin may help you.
Change By:
ikedam
(27/Sep/14 4:59 AM)
Component/s:
build-pipeline
Component/s:
copyartifact
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and 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] [mailer] (JENKINS-24885) SMTP authentication not working from jenkins version 1.576
zhang qeekey created JENKINS-24885 SMTP authentication not working from jenkins version 1.576 Issue Type: Bug Assignee: Unassigned Attachments: buginfo.txt Components: mailer Created: 27/Sep/14 2:53 AM Description: When i finished STMP configrations with correct infomation, and found the function of "Test e-mail recipient" return a error message about "javax.mail.AuthenticationFailedException: 535 authentication failed" and so on. With the same STMP config,it will work very well at jenkins 1.575.Here is some test results about "Test e-mail recipient" of different jenkins versions: jenkinss 1.546 Email was successfully sent jenkinss 1.565 Email was successfully sent jenkinss 1.575 Email was successfully sent jenkinss 1.576 Failed to send out e-mail jenkinss 1.578 Failed to send out e-mail jenkinss 1.580 Failed to send out e-mail jenkinss 1.581 Failed to send out e-mail Environment: Jenkins version:1.581 installed plugins: default plugins operating system: Linux version 2.6.32-220.el6.x86_64 web browser:chrome Java vendor : JDK 1.6.0_45- Project: Jenkins Labels: jenkins Priority: Major Reporter: zhang qeekey This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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-24884) Unable to use SSO with Jenkins + Crowd
Nadav Samet created JENKINS-24884 Unable to use SSO with Jenkins + Crowd Issue Type: Bug Assignee: Kanstantsin Shautsou Components: crowd2 Created: 27/Sep/14 12:49 AM Description: Authentication with the Jenkins plug in work well, however I am unable to use SSO. Expected behavior: 1. Log in at https://crowd.mydomain.com 2. Go to https://jenkins.mydomain.com 3. Get logged in. Actual behavior: 3. Displays login screen. FWIW, SSO works well between JIRA and Crowd. I am not seeing any lines on this misbehavior on neither Crowd or Jenkins log files. Inspecting the HTTP request it appears that the crowd token cookie is sent to Jenkins, and the name (default) is configured correctly in the plugin's configuration. Let me know if additional information is needed. Environment: Jenkins 1.581 on Ubuntu. Crowd 1.8 Plugin Crowd 2.7.2 Jenkins and Crowd are running on SSL behind Apache proxy. Project: Jenkins Priority: Major Reporter: Nadav Samet This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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-24448) Empty changes when building from tag not branch
Mark Waite updated JENKINS-24448 Empty changes when building from tag not branch Change By: Mark Waite (26/Sep/14 10:21 PM) Priority: Blocker Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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-24879) Git Plugin env variable resolution not working in Git Publisher
Mark Waite updated JENKINS-24879 Git Plugin env variable resolution not working in Git Publisher Change By: Mark Waite (26/Sep/14 10:20 PM) Summary: Git Plugin envvariable env variable resolution not working in Git Publisher This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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-24879) Git Plugin envvariable resolution not working in Git Publisher
Mark Waite assigned JENKINS-24879 to Mark Waite Git Plugin envvariable resolution not working in Git Publisher Change By: Mark Waite (26/Sep/14 10:20 PM) Assignee: Nicolas De Loof Mark Waite This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-24883) Artifacts not found on re-runs of manual jobs in pipeline
Matt Jernigan created JENKINS-24883 Artifacts not found on re-runs of manual jobs in pipeline Issue Type: Bug Assignee: Unassigned Components: copyartifact Created: 26/Sep/14 10:07 PM Description: Project A calls project B automatically with "Build other projects". Project B calls project C manually with "Build other projects (manual step)". All artifacts are archived and fingerprinted. Project B is set to copy artifacts from project A with "Upstream build that triggered this job". Project C is set to copy artifacts from project B with "Upstream build that triggered this job". Using the Build Pipeline plugin I can rerun A and/or B as much as I want in various pipeline builds of the same project. Each one moves the correct artifact versions around. I can run C manually once correctly. If I rerun it, it fails with this message: Unable to find a build for artifact copy from: B Repeat tries get repeat failures. If I jump to other pipeline builds of the same project and rerun C there, same thing, more failures. If I restart Jenkins, however, and try again, it will fail once more and then clear C from the pipeline. Then I can run it again without failure. But only once before it starts failing again. My test actually has five projects in a pipeline with the last two manually triggered. Both of these last two fail with the same behavior (even if I don't test all the way to the last project). Environment: Jenkins 1.580 on RHEL and Java 1.7.0_65-b33. Using both Firefox and Chrome. Project: Jenkins Priority: Blocker Reporter: Matt Jernigan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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-19859) Dynamic installation of plugin permitted even when dependencies must be updated first
SCM/JIRA link daemon commented on JENKINS-19859 Dynamic installation of plugin permitted even when dependencies must be updated first Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/test/acceptance/po/PluginManager.java src/main/java/org/jenkinsci/test/acceptance/po/UpdateCenter.java http://jenkins-ci.org/commit/acceptance-test-harness/dae6a9a7271ae91498357d2f615b842d81c1ed84 Log: Yet another @WithPlugins fix, working around JENKINS-19859 this 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] [performance-plugin] (JENKINS-20042) FEEDBACK WANTED: Proposal To Mark Builds As Unstable/Failed Based on Avg Response Time
Dave Leo commented on JENKINS-20042 FEEDBACK WANTED: Proposal To Mark Builds As Unstable/Failed Based on Avg Response Time I am using gradle to run Jmeter, and for some reason it isn't producing .jtl but rather a -MMDD-HH24MI.xml file for the results. So I am trying to use this feature but I cannot get it to work (setting it to 1 ms expecting it to fail but it isn't failing) wondering if the result file being produced is the problem can you allow wildcards there? How does it find a match? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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-10234) Junit result archiver getting stuck for a long time in concurrent builds
Jesse Glick commented on JENKINS-10234 Junit result archiver getting stuck for a long time in concurrent builds Probably too late for 1.565.x and probably already in the next LTS, but marking it as a candidate just in case. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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-10234) Junit result archiver getting stuck for a long time in concurrent builds
Jesse Glick updated JENKINS-10234 Junit result archiver getting stuck for a long time in concurrent builds Change By: Jesse Glick (26/Sep/14 8:30 PM) Labels: checkpoint concurrent lts-candidate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-auth] (JENKINS-24878) Implement super-users ACL so this users can access a job even if "allow a job to not inherit from global ACL" is set to true
Jesse Glick assigned JENKINS-24878 to Unassigned Implement super-users ACL so this users can access a job even if "allow a job to not inherit from global ACL" is set to true Change By: Jesse Glick (26/Sep/14 8:32 PM) Assignee: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-24225) Provide a stats page to display data for a given set of job(s) and period: job, rate of failure, reason for failure, category of failure
J John commented on JENKINS-24225 Provide a stats page to display data for a given set of job(s) and period: job, rate of failure, reason for failure, category of failure Also, it would be great if there is a way to navigate from one error to another in the Console Output page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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] [promoted-builds] (JENKINS-24882) Re-execute button always visible
Matthew Albright created JENKINS-24882 Re-execute button always visible Issue Type: Bug Assignee: Unassigned Components: promoted-builds Created: 26/Sep/14 8:20 PM Description: Re-execute promotion is always visible but forwards the user to a blank screen when a user group is specified as the approver. It looks like the the code is only comparing the logged in user (or anonymous) to the approver. When doing the initial promotion, it is checking to see if the user is a part of any usergroups and comparing those values to the approver. Unless we add users individually, they will not have access to Re-Execute promotion. Project: Jenkins Priority: Major Reporter: Matthew Albright This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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-24881) Rename job starts to sync workspace
Arran Bartish created JENKINS-24881 Rename job starts to sync workspace Issue Type: Bug Assignee: Unassigned Components: scm-sync-configuration Created: 26/Sep/14 8:10 PM Description: When a jenkins instance is running with an active sync plugin there seems to be an issue when a job gets renamed. Steps to reproduce Setup jenkins instance with active sync to a git repository ensure some builds have completed so that a workspace is available rename job which has a work space Expected Result Old job is moved to new job in VCS Actual Job is moved and workspace information is pushed to the repo This also include lastSuccessful references etc. Impact Configuration repo grows to a massive size as binaries start to get synced up to git (~5GB) in our case. Resolution in the event of issue create new repo clone old repo back up config files reset hard until the point before the rename dump your backed up config over the top of the config (brings you to your latest greatest) clean up any jobs that should be deleted set the new repo as your upstream, commit and push reload the config from the new repo This has the drawback of losing history between when things went wrong and when you fixed Environment: Jenkins ver. 1.570 SCM Sync Configuration Plugin ver. 0.0.8 GIT client plugin ver. 1.10.2 GIT plugin ver. 2.2.6 Project: Jenkins Labels: scm configuration sync plugin Priority: Critical Reporter: Arran Bartish This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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-24833) Git Plugin Publisher Publishes on Failed Build even though set to push only if build succeeds
Loren Klingman
edited a comment on JENKINS-24833
Git Plugin Publisher Publishes on Failed Build even though set to push only if build succeeds
Is build status case sensitive in your check? I have two post-build failures that I tried.
One is with xUnit
Building in workspace /var/lib/jenkins/workspace/Test
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url g...@bitbucket.org:wiseloren/finance.git # timeout=10
Fetching upstream changes from g...@bitbucket.org:wiseloren/finance.git
> git --version # timeout=10
> git fetch --tags --progress g...@bitbucket.org:wiseloren/finance.git +refs/heads/:refs/remotes/origin/
> git rev-parse refs/remotes/origin/develop^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/develop^{commit} # timeout=10
Checking out Revision 7553bf2bc81d6086400b9274e52e806e5fc90374 (refs/remotes/origin/develop)
> git config core.sparsecheckout # timeout=10
> git checkout -f 7553bf2bc81d6086400b9274e52e806e5fc90374
> git rev-list 7553bf2bc81d6086400b9274e52e806e5fc90374 # timeout=10
[Test] $ /bin/sh -xe /tmp/hudson4989245979488022036.sh
+ date
+ git add date.txt
+ git commit -m test
[detached HEAD f3d92b4] test
1 file changed, 1 insertion, 1 deletion
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing PHPUnit-3.x (default)
[xUnit] [INFO] - [PHPUnit-3.x (default)] - 1 test report file(s) were found with the pattern 'build/logs/junit.xml' relative to '/var/lib/jenkins/workspace/Test' for the testing framework 'PHPUnit-3.x (default)'.
[xUnit] [ERROR] - Test reports were found but not all of them are new. Did all the tests run?
/var/lib/jenkins/workspace/Test/build/logs/junit.xml is 1 min 41 sec old
[xUnit] [INFO] - Failing BUILD.
[xUnit] [INFO] - There are errors when processing test results.
[xUnit] [INFO] - Skipping tests recording.
[xUnit] [INFO] - Stop build.
Build step 'Publish xUnit test result report' changed build result to FAILURE
Build did not succeed and the project is configured to only push after a successful build, so no pushing will occur.
Finished: FAILURE
The other is with Crap4J
Building in workspace /var/lib/jenkins/workspace/Test
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url g...@bitbucket.org:wiseloren/finance.git # timeout=10
Fetching upstream changes from g...@bitbucket.org:wiseloren/finance.git
> git --version # timeout=10
> git fetch --tags --progress g...@bitbucket.org:wiseloren/finance.git +refs/heads/:refs/remotes/origin/
> git rev-parse refs/remotes/origin/develop^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/develop^{commit} # timeout=10
Checking out Revision 7553bf2bc81d6086400b9274e52e806e5fc90374 (refs/remotes/origin/develop)
> git config core.sparsecheckout # timeout=10
> git checkout -f 7553bf2bc81d6086400b9274e52e806e5fc90374
> git rev-list 7553bf2bc81d6086400b9274e52e806e5fc90374 # timeout=10
[Test] $ /bin/sh -xe /tmp/hudson7046176554547474773.sh
+ date
+ git add date.txt
+ git commit -m test
[detached HEAD 4f7619c] test
1 file changed, 1 insertion, 1 deletion
[CRAP4J] Collecting Crap4J analysis files...
[CRAP4J] Searching for report files within build/logs/crap4j2.xml
[CRAP4J] Using the new FileSetBuilder
[CRAP4J] No crap4j report files were found. Configuration error?
Build step 'Report Crap' marked build as failure
Pushing HEAD to branch develop at repo origin
> git push g...@bitbucket.org:wiseloren/finance.git HEAD:develop*
Finished: FAILURE
In both cases, Jenkins recognizes a job failure, but only in one case does the push not happen. The main difference I'm noticing is that CRAP4J marks it as failure not FAILURE. Thus, I'm thinking Jenkins must be case insensitive where the other plugins are case sensitive. (Your plugin isn't the only one missing the marking as a failure there.) If that is the case, I'll submit a bug request to CRAP4J (though it might be good for your check to be case insensitive since jenkins is).
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] [jira] (JENKINS-18166) Add support for JIRA REST API - JIRA SOAP API will be removed in JIRA 7
Ben McDonie commented on JENKINS-18166 Add support for JIRA REST API - JIRA SOAP API will be removed in JIRA 7 Stefan, how is this new REST plugin coming along? Any progress? I too am interested in a plugin that uses REST. I've been having all kinds of issues with the current plugin in the latest JIRA versions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24833) Git Plugin Publisher Publishes on Failed Build even though set to push only if build succeeds
Loren Klingman
edited a comment on JENKINS-24833
Git Plugin Publisher Publishes on Failed Build even though set to push only if build succeeds
Is build status case sensitive in your check? I have two post-build failures that I tried.
In both cases, Jenkins recognizes a job failure, but only in one case does the push not happen. The main difference I'm noticing is that CRAP4J marks it as failure not FAILURE. Thus, I'm thinking Jenkins must be case insensitive where the other plugins are case sensitive. (Your plugin isn't the only one missing the marking as a failure there.) If that is the case, I'll submit a bug request to CRAP4J (though it might be good for your check to be case insensitive since jenkins is).
One is with xUnit
Building in workspace /var/lib/jenkins/workspace/Test
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url g...@bitbucket.org:wiseloren/finance.git # timeout=10
Fetching upstream changes from g...@bitbucket.org:wiseloren/finance.git
> git --version # timeout=10
> git fetch --tags --progress g...@bitbucket.org:wiseloren/finance.git +refs/heads/:refs/remotes/origin/
> git rev-parse refs/remotes/origin/develop^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/develop^{commit} # timeout=10
Checking out Revision 7553bf2bc81d6086400b9274e52e806e5fc90374 (refs/remotes/origin/develop)
> git config core.sparsecheckout # timeout=10
> git checkout -f 7553bf2bc81d6086400b9274e52e806e5fc90374
> git rev-list 7553bf2bc81d6086400b9274e52e806e5fc90374 # timeout=10
[Test] $ /bin/sh -xe /tmp/hudson4989245979488022036.sh
+ date
+ git add date.txt
+ git commit -m test
[detached HEAD f3d92b4] test
1 file changed, 1 insertion, 1 deletion
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing PHPUnit-3.x (default)
[xUnit] [INFO] - [PHPUnit-3.x (default)] - 1 test report file(s) were found with the pattern 'build/logs/junit.xml' relative to '/var/lib/jenkins/workspace/Test' for the testing framework 'PHPUnit-3.x (default)'.
[xUnit] [ERROR] - Test reports were found but not all of them are new. Did all the tests run?
/var/lib/jenkins/workspace/Test/build/logs/junit.xml is 1 min 41 sec old
[xUnit] [INFO] - Failing BUILD.
[xUnit] [INFO] - There are errors when processing test results.
[xUnit] [INFO] - Skipping tests recording.
[xUnit] [INFO] - Stop build.
Build step 'Publish xUnit test result report' changed build result to FAILURE
Build did not succeed and the project is configured to only push after a successful build, so no pushing will occur.
Finished: FAILURE
The other is with Crap4J
Building in workspace /var/lib/jenkins/workspace/Test
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url g...@bitbucket.org:wiseloren/finance.git # timeout=10
Fetching upstream changes from g...@bitbucket.org:wiseloren/finance.git
> git --version # timeout=10
> git fetch --tags --progress g...@bitbucket.org:wiseloren/finance.git +refs/heads/:refs/remotes/origin/
> git rev-parse refs/remotes/origin/develop^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/develop^{commit} # timeout=10
Checking out Revision 7553bf2bc81d6086400b9274e52e806e5fc90374 (refs/remotes/origin/develop)
> git config core.sparsecheckout # timeout=10
> git checkout -f 7553bf2bc81d6086400b9274e52e806e5fc90374
> git rev-list 7553bf2bc81d6086400b9274e52e806e5fc90374 # timeout=10
[Test] $ /bin/sh -xe /tmp/hudson7046176554547474773.sh
+ date
+ git add date.txt
+ git commit -m test
[detached HEAD 4f7619c] test
1 file changed, 1 insertion, 1 deletion
[CRAP4J] Collecting Crap4J analysis files...
[CRAP4J] Searching for report files within build/logs/crap4j2.xml
[CRAP4J] Using the new FileSetBuilder
[CRAP4J] No crap4j report files were found. Configuration error?
Build step 'Report Crap' marked build as failure
Pushing HEAD to branch develop at repo origin
> git push g...@bitbucket.org:wiseloren/finance.git HEAD:develop
Finished: 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
--
Y
[JIRA] [git] (JENKINS-24833) Git Plugin Publisher Publishes on Failed Build even though set to push only if build succeeds
Loren Klingman
edited a comment on JENKINS-24833
Git Plugin Publisher Publishes on Failed Build even though set to push only if build succeeds
Is build status case sensitive in your check? I have two post-build failures that I tried.
In both cases, Jenkins recognizes a job failure, but only in one case does the push not happen. The main difference I'm noticing is that CRAP4J marks it as failure not FAILURE. Thus, I'm thinking Jenkins must be case insensitive where the other plugins are case sensitive. (Your plugin isn't the only one missing the marking as a failure there.) If that is the case, I'll submit a bug request to CRAP4J (though it might be good for your check to be case insensitive since jenkins is).
One is with xUnit
Building in workspace /var/lib/jenkins/workspace/Test
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url g...@bitbucket.org:wiseloren/finance.git # timeout=10
Fetching upstream changes from g...@bitbucket.org:wiseloren/finance.git
> git --version # timeout=10
> git fetch --tags --progress g...@bitbucket.org:wiseloren/finance.git +refs/heads/:refs/remotes/origin/
> git rev-parse refs/remotes/origin/develop^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/develop^{commit} # timeout=10
Checking out Revision 7553bf2bc81d6086400b9274e52e806e5fc90374 (refs/remotes/origin/develop)
> git config core.sparsecheckout # timeout=10
> git checkout -f 7553bf2bc81d6086400b9274e52e806e5fc90374
> git rev-list 7553bf2bc81d6086400b9274e52e806e5fc90374 # timeout=10
[Test] $ /bin/sh -xe /tmp/hudson4989245979488022036.sh
+ date
+ git add date.txt
+ git commit -m test
[detached HEAD f3d92b4] test
1 file changed, 1 insertion, 1 deletion
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing PHPUnit-3.x (default)
[xUnit] [INFO] - [PHPUnit-3.x (default)] - 1 test report file(s) were found with the pattern 'build/logs/junit.xml' relative to '/var/lib/jenkins/workspace/Test' for the testing framework 'PHPUnit-3.x (default)'.
[xUnit] [ERROR] - Test reports were found but not all of them are new. Did all the tests run?
/var/lib/jenkins/workspace/Test/build/logs/junit.xml is 1 min 41 sec old
[xUnit] [INFO] - Failing BUILD.
[xUnit] [INFO] - There are errors when processing test results.
[xUnit] [INFO] - Skipping tests recording.
[xUnit] [INFO] - Stop build.
Build step 'Publish xUnit test result report' changed build result to FAILURE
Build did not succeed and the project is configured to only push after a successful build, so no pushing will occur.
Finished: FAILURE
The other is with Crap4J
Building in workspace /var/lib/jenkins/workspace/Test
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url g...@bitbucket.org:wiseloren/finance.git # timeout=10
Fetching upstream changes from g...@bitbucket.org:wiseloren/finance.git
> git --version # timeout=10
> git fetch --tags --progress g...@bitbucket.org:wiseloren/finance.git +refs/heads/:refs/remotes/origin/
> git rev-parse refs/remotes/origin/develop^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/develop^{commit} # timeout=10
Checking out Revision 7553bf2bc81d6086400b9274e52e806e5fc90374 (refs/remotes/origin/develop)
> git config core.sparsecheckout # timeout=10
> git checkout -f 7553bf2bc81d6086400b9274e52e806e5fc90374
> git rev-list 7553bf2bc81d6086400b9274e52e806e5fc90374 # timeout=10
[Test] $ /bin/sh -xe /tmp/hudson7046176554547474773.sh
+ date
+ git add date.txt
+ git commit -m test
[detached HEAD 4f7619c] test
1 file changed, 1 insertion, 1 deletion
[CRAP4J] Collecting Crap4J analysis files...
[CRAP4J] Searching for report files within build/logs/crap4j2.xml
[CRAP4J] Using the new FileSetBuilder
[CRAP4J] No crap4j report files were found. Configuration error?
Build step 'Report Crap' marked build as failure
Pushing HEAD to branch develop at repo origin
> git push g...@bitbucket.org:wiseloren/finance.git HEAD:develop*
Finished: 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
[JIRA] [git] (JENKINS-24833) Git Plugin Publisher Publishes on Failed Build even though set to push only if build succeeds
Loren Klingman
commented on JENKINS-24833
Git Plugin Publisher Publishes on Failed Build even though set to push only if build succeeds
Is build status case sensitive in your check? I have two post-build failures that I tried.
One is with xUnit{/color:red}
Building in workspace /var/lib/jenkins/workspace/Test
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url g...@bitbucket.org:wiseloren/finance.git # timeout=10
Fetching upstream changes from g...@bitbucket.org:wiseloren/finance.git
> git --version # timeout=10
> git fetch --tags --progress g...@bitbucket.org:wiseloren/finance.git +refs/heads/:refs/remotes/origin/
> git rev-parse refs/remotes/origin/develop^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/develop^{commit} # timeout=10
Checking out Revision 7553bf2bc81d6086400b9274e52e806e5fc90374 (refs/remotes/origin/develop)
> git config core.sparsecheckout # timeout=10
> git checkout -f 7553bf2bc81d6086400b9274e52e806e5fc90374
> git rev-list 7553bf2bc81d6086400b9274e52e806e5fc90374 # timeout=10
[Test] $ /bin/sh -xe /tmp/hudson4989245979488022036.sh
+ date
+ git add date.txt
+ git commit -m test
[detached HEAD f3d92b4] test
1 file changed, 1 insertion, 1 deletion
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing PHPUnit-3.x (default)
[xUnit] [INFO] - [PHPUnit-3.x (default)] - 1 test report file(s) were found with the pattern 'build/logs/junit.xml' relative to '/var/lib/jenkins/workspace/Test' for the testing framework 'PHPUnit-3.x (default)'.
[xUnit] [ERROR] - Test reports were found but not all of them are new. Did all the tests run?
/var/lib/jenkins/workspace/Test/build/logs/junit.xml is 1 min 41 sec old
[xUnit] [INFO] - Failing BUILD.
[xUnit] [INFO] - There are errors when processing test results.
[xUnit] [INFO] - Skipping tests recording.
[xUnit] [INFO] - Stop build.
Build step 'Publish xUnit test result report' changed build result to FAILURE
Build did not succeed and the project is configured to only push after a successful build, so no pushing will occur.
Finished: FAILURE
Crap4J{/color:red}
Building in workspace /var/lib/jenkins/workspace/Test
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url g...@bitbucket.org:wiseloren/finance.git # timeout=10
Fetching upstream changes from g...@bitbucket.org:wiseloren/finance.git
> git --version # timeout=10
> git fetch --tags --progress g...@bitbucket.org:wiseloren/finance.git +refs/heads/:refs/remotes/origin/
> git rev-parse refs/remotes/origin/develop^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/develop^{commit} # timeout=10
Checking out Revision 7553bf2bc81d6086400b9274e52e806e5fc90374 (refs/remotes/origin/develop)
> git config core.sparsecheckout # timeout=10
> git checkout -f 7553bf2bc81d6086400b9274e52e806e5fc90374
> git rev-list 7553bf2bc81d6086400b9274e52e806e5fc90374 # timeout=10
[Test] $ /bin/sh -xe /tmp/hudson7046176554547474773.sh
+ date
+ git add date.txt
+ git commit -m test
[detached HEAD 4f7619c] test
1 file changed, 1 insertion, 1 deletion
[CRAP4J] Collecting Crap4J analysis files...
[CRAP4J] Searching for report files within build/logs/crap4j2.xml
[CRAP4J] Using the new FileSetBuilder
[CRAP4J] No crap4j report files were found. Configuration error?
Build step 'Report Crap' marked build as failure
Pushing HEAD to branch develop at repo origin
> git push g...@bitbucket.org:wiseloren/finance.git HEAD:develop*
Finished: FAILURE
In both cases, Jenkins recognizes a job failure, but only in one case does the push not happen. The main difference I'm noticing is that CRAP4J marks it as failure not FAILURE. Thus, I'm thinking Jenkins must be case insensitive where the other plugins are case sensitive. (Your plugin isn't the only one missing the marking as a failure there.) If that is the case, I'll submit a bug request to CRAP4J (though it might be good for your check to be case insensitive since jenkins is).
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] [core] (JENKINS-24357) Jenkins 1.535+ versions do not work on Solaris 10
Daniel Beck commented on JENKINS-24357 Jenkins 1.535+ versions do not work on Solaris 10 45 GC threads immediately after start, and 98% used in the permgen... I'd try to look into setting a larger permgen using Java command line args, or maybe throttle the GC. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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-24880) Support publishing a list of tags resolved from an environment variable
Michael O'Cleirigh created JENKINS-24880 Support publishing a list of tags resolved from an environment variable Issue Type: Improvement Assignee: Unassigned Components: git Created: 26/Sep/14 6:22 PM Description: I have the need to be able to create multiple tags as part of a release in the same repository. Using the EnvInject plugin I can setup an environment variable that contains the name of all of the created tags. What I need is for the GitPublisher to be able to expand a comma delimited string variable and submit a seperate push request for each element in the list. Project: Jenkins Labels: jenkins plugin git Priority: Major Reporter: Michael O'Cleirigh This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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-24869) POM_VERSION is not resetted
tobias schaber updated JENKINS-24869 POM_VERSION is not resetted Change By: tobias schaber (26/Sep/14 5:39 PM) Labels: maven This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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-24879) Git Plugin envvariable resolution not working in Git Publisher
tobias schaber
created JENKINS-24879
Git Plugin envvariable resolution not working in Git Publisher
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
git
Created:
26/Sep/14 5:37 PM
Description:
Hi,
I'm using Git in a Jenkins process with the following URL:
http://192.168.0.17:7990/scm/sour/${REPO_NAME}.git
where REPO_NAME is given as a Parameter to the Job.
The Source Code Checkout works fine, the URL can be resolved with the variable in it.
At the end of the process I use the "Git Publisher" Post Build Action with following configuration:
Push Only If Build Succeeded (true)
Tag to push $TAG_NAME
Tag message ...
Create new tag (true)
Target remote Name: sources_repo
But now, the GIT URL from above can not be resolved as the variable REPO_NAME can not be resolved. The process Fails with the following exception:
Pushing tag testapp-1.0.0-58 to repo sources_repo
ERROR: Failed to push tag testapp-1.0.0-58 to sources_repo
hudson.plugins.git.GitException: Invalid URL http://192.168.0.17:7990/scm/sour/${REPO_NAME}.git
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkCredentials(CliGitAPIImpl.java:2259)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1171)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:87)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$7.execute(CliGitAPIImpl.java:1492)
at hudson.plugins.git.GitPublisher.perform(GitPublisher.java:298)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1040)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)
at hudson.model.Run.execute(Run.java:1770)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Build step 'Git Publisher' marked build as failure
Maybe you could have an eye on this?
Kind regards,
Tobias
Environment:
Jenkins 1.581
Git Plugin 2.2.6
Project:
Jenkins
Priority:
Minor
Reporter:
tobias schaber
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and 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-10234) Junit result archiver getting stuck for a long time in concurrent builds
Henrik Skupin commented on JENKINS-10234 Junit result archiver getting stuck for a long time in concurrent builds Any change that we could get this backported to the 1.565.x LTS branch? It's one of the most annoying problems for our Jenkins production systems. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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-22514) Zip generated from "all files in zip" contains the wrong slashes
Daniel Beck assigned JENKINS-22514 to Holger Voormann Zip generated from "all files in zip" contains the wrong slashes Holger took over, so assigning the issue to him. Change By: Daniel Beck (26/Sep/14 5:31 PM) Assignee: Daniel Beck Holger Voormann This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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] [matrix-auth] (JENKINS-24878) Implement super-users ACL so this users can access a job even if "allow a job to not inherit from global ACL" is set to true
Alexandre Zia created JENKINS-24878 Implement super-users ACL so this users can access a job even if "allow a job to not inherit from global ACL" is set to true Issue Type: Improvement Assignee: Jesse Glick Components: matrix-auth Created: 26/Sep/14 5:28 PM Description: Ticket: JENKINS-10593 has implemented "allow a job to not inherit from global ACL" However, it would be great to have a global permission where you can flag a user as a super-admin which can have access to all jobs even if it has "allow a job to not inherit from global ACL" set to true The reason is we have an infrastructure team which manages Jenkins access, and sometimes a team enables "allow a job to not inherit from global ACL" and infra team loses access to this job. Or even if the admins of a job leave the company, super-users with access to all jobs even if "allow a job to not inherit from global ACL" is true must access it to reassign permissions Thanks in advance Project: Jenkins Priority: Major Reporter: Alexandre Zia This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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-slaves] (JENKINS-24877) ssh slaves 1.7 breaks slaves without defined timeout values
Trent Geerdes created JENKINS-24877 ssh slaves 1.7 breaks slaves without defined timeout values Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: ssh-slaves Created: 26/Sep/14 5:14 PM Description: Upgrading ssh-slaves from 1.6 to 1.7 made all slaves fail to connect. Adding timeout and retry values to empty fields in the slave configurations allowed them to connect again. Environment: jenkins 1.581 on centos 6.4; upgrading ssh-slaves from 1.6 to 1.7 Project: Jenkins Priority: Minor Reporter: Trent Geerdes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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-22514) Zip generated from "all files in zip" contains the wrong slashes
Harald Hermann commented on JENKINS-22514 Zip generated from "all files in zip" contains the wrong slashes Thanks Holger for the quick response and commit. We hope this gets soon integrated so we can upgrade. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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-22514) Zip generated from "all files in zip" contains the wrong slashes
Holger Voormann commented on JENKINS-22514 Zip generated from "all files in zip" contains the wrong slashes Pull request: https://github.com/jenkinsci/jenkins/pull/1408 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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] [project-inheritance] (JENKINS-19819) Trigger Parameterized Build Defined on Abstract Job is Not Triggered by Concrete Jobs
Mike Murray commented on JENKINS-19819 Trigger Parameterized Build Defined on Abstract Job is Not Triggered by Concrete Jobs I'm not aware of any. We implemented the desired behavior in the concrete classes, rather than rely on the expected abstract 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] [project-inheritance] (JENKINS-19819) Trigger Parameterized Build Defined on Abstract Job is Not Triggered by Concrete Jobs
Helmut Schaa commented on JENKINS-19819 Trigger Parameterized Build Defined on Abstract Job is Not Triggered by Concrete Jobs Just stumbled over the same issue. Are there any workarounds for this issue yet? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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] [deploy] (JENKINS-24876) [Deploy plugin] need to parameterize deploy host and port
Verny Quartara Gutierrez started work on JENKINS-24876 [Deploy plugin] need to parameterize deploy host and port Change By: Verny Quartara Gutierrez (26/Sep/14 3:30 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [deploy] (JENKINS-24876) [Deploy plugin] need to parameterize deploy host and port
Verny Quartara Gutierrez updated JENKINS-24876 [Deploy plugin] need to parameterize deploy host and port Change By: Verny Quartara Gutierrez (26/Sep/14 3:28 PM) Summary: [Deploy plugin] need to parameterize deploy host and port This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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] [deploy] (JENKINS-24876) need to parameterize deploy host and port
Verny Quartara Gutierrez created JENKINS-24876 need to parameterize deploy host and port Issue Type: Improvement Assignee: Verny Quartara Gutierrez Components: deploy Created: 26/Sep/14 3:28 PM Description: I need to parametrize the server host and port to deploy to, as already requested in others issues. I forked the repo and looked at the code: it seems to me that this feature isn't supported. I'm going to develop the new feature, then I'll send a pull request. Please inform me if someone is working on the same issue. Thanks Environment: jenkins 1.577 deploy plugin 1.10 Project: Jenkins Labels: parameter parameterized Priority: Major Reporter: Verny Quartara Gutierrez This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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-flow] (JENKINS-24875) Build-flow version 0.14 and 0.15 does not show any build-graph (buildgraph-view 1.1.1)
Per Böhlin created JENKINS-24875 Build-flow version 0.14 and 0.15 does not show any build-graph (buildgraph-view 1.1.1) Issue Type: Bug Assignee: Nicolas De Loof Components: build-flow Created: 26/Sep/14 3:21 PM Description: When using build-flow version 0.14 or version 0.15 together with buildgraph-view 1.1.1 on jenkins versions 1.577 and 1.561 the graph doesn't show at all. By downgrading to build-flow 0.12 the build-graph is shown correctly, even for old builds. I have not tried build-flow 0.13 so I don't know if that version is also affected. Environment: Jenkins 1.577 and 1.561 Build-flow version 0.14 and 0.15 buildgraph-view 1.1.1 parameterized-trigger 2.25 Linux Ubuntu 14.04 LTS Project: Jenkins Priority: Major Reporter: Per Böhlin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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] [xcode] (JENKINS-24874) Xcode plugin hangs when using xcode6
Reinhard Karbas created JENKINS-24874 Xcode plugin hangs when using xcode6 Issue Type: Bug Assignee: Unassigned Components: xcode Created: 26/Sep/14 2:48 PM Description: We have several components to build in one Jenkins job calling the xCode plugin several times The first two builds work, however the 3rd instance of the build gets stuck after the clean and never gets to the build step First build: [openssl-ios] $ /usr/bin/xcodebuild -version Xcode 6.0.1 Build version 6A317 Cleaning build directory: /Users/Jenkins/Ansible/Mobile3rdParty/openssl-ios/build/Release-iphoneos === == Available provisioning profiles [openssl-ios] $ /usr/bin/security find-identity -p codesigning -v 1) A0C22EDB47D2DFC413DCD56967B86D28B1374342 "Developer ID Application: Siemens Enterprise Communications GmbH & Co. KG" 2) C19DB47077CAC502936224069C5218D77D163404 "iPhone Developer: Simon Hall (BDNNEYZ3AQ)" 3) F25A1E6F9A4774208A8C590C1953493BDEE6F005 "iPhone Distribution: Siemens Enterprise Communications, Inc." 3 valid identities found == Available SDKs [openssl-ios] $ /usr/bin/xcodebuild -showsdks OS X SDKs: OS X 10.9 -sdk macosx10.9 iOS SDKs: iOS 8.0 -sdk iphoneos8.0 iOS Simulator SDKs: Simulator - iOS 8.0 -sdk iphonesimulator8.0 == Available schemes [openssl-ios] $ /usr/bin/xcodebuild -list -project openssl.xcodeproj Information about project "openssl": Targets: crypto ssl Build Configurations: Debug Release Distribution If no build configuration is specified and -scheme is not passed then "Release" is used. Schemes: crypto ssl === Going to invoke xcodebuild:target: ALL, sdk: DEFAULT, project: openssl.xcodeproj, configuration: Release, clean: YES, archive:NO, symRoot: DEFAULT, configurationBuildDir: DEFAULT, codeSignIdentity: DEFAULT [openssl-ios] $ /usr/bin/xcodebuild -alltargets -project openssl.xcodeproj -configuration Release clean build === CLEAN TARGET crypto OF PROJECT openssl WITH CONFIGURATION Release === Second build: Cleaning build directory: /Users/Jenkins/Ansible/Mobile3rdParty/ZipArchive/build/Release-iphoneos === == Available provisioning profiles [ZipArchive] $ /usr/bin/security find-identity -p codesigning -v 1) A0C22EDB47D2DFC413DCD56967B86D28B1374342 "Developer ID Application: Siemens Enterprise Communications GmbH & Co. KG" 2) C19DB47077CAC502936224069C5218D77D163404 "iPhone Developer: Simon Hall (BDNNEYZ3AQ)" 3) F25A1E6F9A4774208A8C590C1953493BDEE6F005 "iPhone Distribution: Siemens Enterprise Communications, Inc." 3 valid identities found == Available SDKs [ZipArchive] $ /usr/bin/xcodebuild -showsdks OS X SDKs: OS X 10.9 -sdk macosx10.9 iOS SDKs: iOS 8.0 -sdk iphoneos8.0 iOS Simulator SDKs: Simulator - iOS 8.0 -sdk iphonesimulator8.0 == Available schemes [ZipArchive] $ /usr/bin/xcodebuild -list -project ZipArchive.xcodeproj Information about project "ZipArchive": Targets: ZipArchive Build Configurations: Debug Distribution Release If no build configuration is specified and -scheme is not passed then "Debug" is used. Schemes: ZipArchive === Going to invoke xcodebuild:target: ZipArchive, sdk: DEFAULT, project: ZipArchive.xcodeproj, configuration: Release, clean: YES, archive:NO, symRoot: DEFAULT, configurationBuildDir: DEFAULT, codeSignIdentity: DEFAULT [ZipArchive] $ /usr/bin/xcodebuild -target ZipArchive -project ZipArchive.xcodeproj -configuration Release clean build === CLEAN TARGET ZipArchive OF PROJECT ZipArchive WITH CONFIGURATION Release === Third build: Cleaning build directory: /Users/Jenkins/Ansible/Mobile3rdParty/WebRTC/trunk/build/Release-iphoneos === == Available provisioning profiles
[JIRA] [ownership] (JENKINS-24475) Managing ownership not possible
Stephan Krull edited a comment on JENKINS-24475 Managing ownership not possible I saw that you released version 0.5. So I did another test today. Jenkins 1.565.1 (I know there is a 1.565.2 meanwhile); JDK6 on Ubuntu 10.04.4 LTS; running JDK6_HOME/bin/java -jar jenkins.war with a clean USER_HOME/.jenkins/ installed ownership plugin 0.4; system configuration: setting global ownership options "Setup after creation" and "Require Configure rights" to true global security configuration: Jenkins internal user management registered a user logged in as the user created a job after creation the user is the owner of that job trying to "manage owners" I get the redirect that is described in this bug While resetting JENKINS_DATA_HOME and installing version 0.5 instead of 0.4 this bug cannot be reproduced. I just acknowledged another thing with 0.5: When creating a new job, as a registered and logged in user, after confirmation of the job form the user is not owner of that plugin see here: In (the now working) dialog of "manage owners" the plugin knows the owner very well: see here the moment I wanted to take the screenshot the bug reoccured. Kind of frustrating. I hope you can reproduce that. One thing I can confirm: If I uncheck the global option "Require Configure rights" the managing of ownership on a job is successful. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ownership] (JENKINS-24475) Managing ownership not possible
Stephan Krull commented on JENKINS-24475 Managing ownership not possible I saw that you released version 0.5. So I did another test today. Jenkins 1.565.1 (I know there is a 1.565.2 meanwhile); JDK6 on Ubuntu 10.04.4 LTS; running JDK6_HOME/bin/java -jar jenkins.war with a clean USER_HOME/.jenkins/ installed ownership plugin 0.4; system configuration: setting global ownership options "Setup after creation" and "Require Configure rights" to true global security configuration: Jenkins internal user management registered a user logged in as the user created a job after creation the user is the owner of that job trying to "manage owners" I get the redirect that is described in this bug While resetting JENKINS_DATA_HOME and installing version 0.5 instead of 0.4 this bug cannot be reproduced. I just acknowledged another thing with 0.5: When creating a new job, as a registered and logged in user, after confirmation of the job form the user is not owner of that plugin see here: This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ownership] (JENKINS-24475) Managing ownership not possible
Stephan Krull updated JENKINS-24475 Managing ownership not possible Change By: Stephan Krull (26/Sep/14 2:15 PM) Attachment: job_summary.png Attachment: logged_in.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker] (JENKINS-23301) Cannot connect to Docker using unix protocol
Jesse Glick commented on JENKINS-23301 Cannot connect to Docker using unix protocol Presumably the jDocker library needs a dep on com.github.jnr:jnr-unixsocket or similar. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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] [pmd] (JENKINS-24873) Wrong number of new warnings
Sergey Ryazantsev updated JENKINS-24873 Wrong number of new warnings Change By: Sergey Ryazantsev (26/Sep/14 1:50 PM) Description: ello Hello .I've got a problem with computing new warnings functional.When I add a new PMD rule to my ruleset, I get odd results.Test case:# Start the first build. See [summary|^build_1_sum.png] and [full|^build_1_full.png] results.# Add a new PMD rule to rule set and start the second build. Rule 'LongVariable' was added. The [summary|^build_2_sum.png] contains only 192 new warnings instead of 267 (==[3126|^build_2_sum.png]-[2859|^build_1_sum.png]). Moreover, [full|^build_2_full.png] result contains 267 warning for new 'LongVariable' rule (match against [first result|^build_1_full.png]).# Go to job configuration, check 'Use delta for new warnings' check box and start the third build. The result changed. The [summary|^build_3_sum.png] contains both 192 and 267 new warnings on the same page. Besides, link '267 new warnings' opens a page with 192 new warnings.I suppose that the number of new warning should always be 267 in the example. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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-24833) Git Plugin Publisher Publishes on Failed Build even though set to push only if build succeeds
Mark Waite commented on JENKINS-24833 Git Plugin Publisher Publishes on Failed Build even though set to push only if build succeeds Loren Klingman I tried to duplicate the problem you're seeing with a smaller case and couldn't. Could you attempt to narrow the failure mode further? I tried: Create a freestyle job JENKINS-24833-git-publishes-always Configure it to use a git repository Add an XShell build step "python add_a_file.py" which runs a python script to add a file to the repo Add a git publisher step to push to the origin remote, master branch Confirm that job succeeds and the change is pushed Add a failing build step after the XShell build step (I used XShell with the command "false" and I used a call to ant) Confirm that job fails and the change is not pushed I also tried a variation: Add a failing post build action (I used publish JUnit reports when the job has no JUnit 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] [pmd] (JENKINS-24873) Wrong number of new warnings
Sergey Ryazantsev created JENKINS-24873 Wrong number of new warnings Issue Type: Bug Assignee: Ulli Hafner Attachments: build_1_full.png, build_1_sum.png, build_2_full.png, build_2_sum.png, build_3_full.png, build_3_sum.png Components: pmd, warnings Created: 26/Sep/14 12:55 PM Description: ello. I've got a problem with computing new warnings functional. When I add a new PMD rule to my ruleset, I get odd results. Test case: Start the first build. See summary and full results. Add a new PMD rule to rule set and start the second build. Rule 'LongVariable' was added. The summary contains only 192 new warnings instead of 267 (==3126-2859). Moreover, full result contains 267 warning for new 'LongVariable' rule (match against first result). Go to job configuration, check 'Use delta for new warnings' check box and start the third build. The result changed. The summary contains both 192 and 267 new warnings on the same page. Besides, link '267 new warnings' opens a page with 192 new warnings. I suppose that the number of new warning should always be 267 in the example. Environment: Jenkins v. 1.554.2 PMD Plugin v. 3.38. Analysis Collector Plugin v. 1.58 Project: Jenkins Labels: pmd warnings Priority: Major Reporter: Sergey Ryazantsev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and 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-22941) Way to mark an Executable that should not block isReadyToRestart
Jesse Glick updated JENKINS-22941 Way to mark an Executable that should not block isReadyToRestart Change By: Jesse Glick (26/Sep/14 12:49 PM) Labels: api workflow This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger] (JENKINS-24872) Job fails when using a blocking parameterized remote trigger with a job name containing a token
Wilco Greven created JENKINS-24872 Job fails when using a blocking parameterized remote trigger with a job name containing a token Issue Type: Bug Assignee: Maurice W. Components: parameterized-remote-trigger Created: 26/Sep/14 12:48 PM Description: We have a Jenkins job with a parameterized-remote-trigger build step. The trigger is configured to block until the remote triggered projects finish their builds. The remote job name contains a token. What we see is that the remote job is triggered succesfully. But polling the status of the remote job fails, because in the URL that is used for polling the token is not substituted. Environment: jenkins 1.565.2 parameterized-remote-trigger 2.1.3 Project: Jenkins Priority: Major Reporter: Wilco Greven This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
