date:20160704

[JIRA] (JENKINS-36426) How to poll two different folder under a single branch in single job

2016-07-04 Thread shubham.j...@amdocs.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Shubham Jain created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36426  
 
 
  How to poll two different folder under a single branch in single job   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 p4-plugin  
 
 
Created: 
 2016/Jul/05 5:50 AM  
 
 
Environment: 
 OS :- Red Hat Enterprise Linux Server release 6.5 (Santiago)  JDK :- 1.7.0_10  Jenkins Version :- Jenkins ver. 1.565  Container :- weblogic  Web Browser :- Chrome and IE  
 
 
Labels: 
 p4plugin jenkins  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Shubham Jain  
 

  
 
 
 
 

 
 We are trying to sync the codes from two different folder of same branch in two different workspaces. But only the last one which is defined in view map is synced. And the other one is not polled by the automatic build. To give a better understanding of the issue, we have the following two lines in view map of our job :- //OSSLEV3/Dev_R4/Cramer/... //LEVEL3_ARMMNGP_P1_THIN_FLOW_R4/... //OSSLEV3/Dev_R4/MNGP/... //L3-MNGP-build_R4/... Ideally, it should poll and read the changes from both the folders, but that is not the case. It is only reading from the last folder.

[JIRA] (JENKINS-36410) Jenkins fails to calculate Assertions while executing a Jmeter script and shows the build status as Success everytime.

2016-07-04 Thread sb00353...@techmahindra.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Bharat Kurmadasu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36410  
 
 
  Jenkins fails to calculate Assertions while executing a Jmeter script and shows the build status as Success everytime.   
 

  
 
 
 
 

 
Change By: 
 Bharat Kurmadasu  
 

  
 
 
 
 

 
 Hi As To execute  a  part of Integrating Jenkins with  Jmeter  tool   script from Jenkins , I have prepared few Jmeter scripts by inserting some assertions like duration assertion, compare assertions  and saved the scripts on local machine .Used 'Performance plugin'  for integration  to save the reports  and  calculate error thresholds and  performed few builds using same script but after completing the build, *Jenkins is unable to calculate the Assertions* and showing the *build result as 'Success' everytime*, though the defined assertion is failing when executed the script in Jmeter tool.Please suggest if I have to enable any extra Assertion/SLA configurations in Jmeter and also if there are any other plugins that I can use in Jenkins to calculate the defined Assertions  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[JIRA] (JENKINS-36211) Karaoke mode: User should follow along with stages when watching a pipeline result execute

2016-07-04 Thread mne...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-36211  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Karaoke mode: User should follow along with stages when watching a pipeline result execute   
 

  
 
 
 
 

 
 Thorsten Scherler looking great! so from what I can tell the confusing bit now is how to get back into the state of following along with the progress?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] (JENKINS-36113) Error while creating a tag in Promotion step

2016-07-04 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36113  
 
 
  Error while creating a tag in Promotion step   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 

  
 
 
 
 

 
 During a promotion of a succesfull build, I try to create and publish an new tag if build is  successfull  successful .In the Promotion / Action / Git publisher box I enter:Push Only If build Succeeds : Checked,Tags : - *tags to push* : ${release} - *Tag message* : The release ${release} from CI automatic build promotion - *Create new tag* : checked - *Target remote name* : originThe git clone is configured as : - *Repository URL* : git@forge-git:/datas/git/.git - *Name* : origin - *Branch specifier* : ${forgeRelease}Where : ${release} is frg1.14.0 and ${forgeRelease} is masterThe promotion fails with the following error :  { { noformat} Started by user jmcBuilding in workspace /datas/jenkins/jobs/forge-forgeCI-start/workspacePromoting forge-forgeCI-start #33failed build hudson.plugins.git.GitPublisher@35d1f590 SUCCESSFinished: FAILURE {noformat } } Without any more explanation. jenkins.log doesn't say more. I try many combinaison without success. Any help would be greatly appreciated.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[JIRA] (JENKINS-36337) Git plugin can't auto get the changes from gitlab when use http://IP/xx.git

2016-07-04 Thread rexuekongl...@163.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 ying zhang commented on  JENKINS-36337  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git plugin can't auto get the changes from gitlab when use http://IP/xx.git   
 

  
 
 
 
 

 
 I found the solution, both the jenkins master and the code build server (slave) had to update the git version.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] (JENKINS-36425) Move non-multibranch run button into header

2016-07-04 Thread jdu...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36425  
 
 
  Move non-multibranch run button into header   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 1.0-m12  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] (JENKINS-36425) Move non-multibranch run button into header

2016-07-04 Thread jdu...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36425  
 
 
  Move non-multibranch run button into header   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 James Dumay  
 
 
Attachments: 
 blueocean.sketch 2016-07-05 11-02-13.png  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Jul/05 1:03 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 James Dumay  
 

  
 
 
 
 

 
 In Scope 
 
Move the non-multibranch run button from the content area into the header as per mockup 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-36419) git plugin 2.5.1 breaks multibranch pipeline if using github source control

2016-07-04 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fix in git plugin 2.5.2 released 4 Jul 2016.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-36419  
 
 
  git plugin 2.5.1 breaks multibranch pipeline if using github source control   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed

2016-07-04 Thread jtel...@flexerasoftware.com (JIRA)

Title: Message Title

James Telfer commented on JENKINS-9104

Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed

FWIW, we implemented a workaround to this issue that doesn't involve wiping out the BUILD_ID variable (as we need to use it). Having a release with the Veto would be better, but this avoids random crashes in the meantime. Instead of allowing the MSBuild process to start the daemon itself, you cause the daemon to start using an environment that you choose. MSBuild then just uses the instance you started rather than starting its own. The Powershell we use is as follows. Use the Powershell plugin to run this as a step before the MSBuild plugin step (could be translated to Windows batch too if you like).

# https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller

var originalBuildID = $Env:BUILD_ID
$Env:BUILD_ID = "DoNotKillMe"
try
{
start mspdbsrv -argumentlist '-start','-spawn' -NoNewWindow
}
catch {}
$Env:BUILD_ID = originalBuildID

Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

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

1 2 >

1 - 100 of 128 matches

Mail list logo