[JIRA] [build-name-setter-plugin] (JENKINS-34512) error in build-name-setter plugin - Set build name

2016-06-03 Thread devesh....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Devesh Kumar commented on  JENKINS-34512 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: error in build-name-setter plugin - Set build name  
 
 
 
 
 
 
 
 
 
 
oh just noticed that.. thanks for sticking with me for long. Really appreciated. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-name-setter-plugin] (JENKINS-34512) error in build-name-setter plugin - Set build name

2016-06-03 Thread devesh....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Devesh Kumar commented on  JENKINS-34512 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: error in build-name-setter plugin - Set build name  
 
 
 
 
 
 
 
 
 
 
Here are the logs, I have removed Visual Studio logs for clarity: 
Started by user Devesh Kumar [EnvInject] - Loading node environment variables. Building in workspace D:\Jenkins\workspace\CCTFinanceBroker Updating https://***MASKED/trunk/src/FinanceBroker at revision '2016-04-28T16:51:59.368 -0400' At revision 49956 no change for https://***MASKED/trunk/src/FinanceBroker since the previous build No emails were triggered. Set build name. New build name is '#553' Path To MSBuild.exe: C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe Executing the command cmd.exe /C " C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe /t:Clean,Rebuild "/p:Configuration=Release,platform=Any CPU" FinanceBrokerServices\FinanceBroker.sln " && exit %%ERRORLEVEL%% from D:\Jenkins\workspace\CCTFinanceBroker [CCTFinanceBroker] $ cmd.exe /C " C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe /t:Clean,Rebuild "/p:Configuration=Release,platform=Any CPU" FinanceBrokerServices\FinanceBroker.sln " && exit %%ERRORLEVEL%% Microsoft (R) Build Engine version 4.0.30319.34209 [Microsoft .NET Framework, version 4.0.30319.34209] Copyright (C) Microsoft Corporation. All rights reserved. 
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch. Build started 4/28/2016 4:52:02 PM. Project "D:\Jenkins\workspace\CCTFinanceBroker\FinanceBrokerServices\FinanceBroker.sln" on node 1 (Clean;Rebuild target(s)). ValidateSolutionConfiguration: Building solution configuration "Release|Any CPU". * * * * Visual Studio build logs MASKED * * * * * Time Elapsed 00:00:00.32 Build step 'Build a Visual Studio project or solution using MSBuild' marked build as failure Set build name. New build name is '#553' Variable with name 'BUILD_DISPLAY_NAME' already exists, current value: '#553', new value: '#553' Recording NUnit tests results Started calculate disk usage of build Finished Calculation of disk usage of build in 0 seconds Started calculate disk usage of workspace Finished Calculation of disk usage of workspace in 0 seconds Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Sending email to: * Finished: FAILURE 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
   

[JIRA] [build-name-setter-plugin] (JENKINS-34512) error in build-name-setter plugin - Set build name

2016-05-31 Thread devesh....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Devesh Kumar commented on  JENKINS-34512 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: error in build-name-setter plugin - Set build name  
 
 
 
 
 
 
 
 
 
 
Yes the build fails and it happens with all my jobs which uses this plugin version. I was able to get a successful build after reverting to the mentioned version. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [svn-tag-plugin] (JENKINS-34569) Subversion tagging fails on Jenkins 2.1

2016-05-03 Thread devesh....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Devesh Kumar created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34569 
 
 
 
  Subversion tagging fails on Jenkins 2.1  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 k2nakamura 
 
 
 

Attachments:
 

 svn-tag.jpg 
 
 
 

Components:
 

 svn-tag-plugin 
 
 
 

Created:
 

 2016/May/03 3:14 PM 
 
 
 

Environment:
 

 OS: Windows Server 2008 R2 Ent./64 bit  Jenkins - 2.1 - Only Master no Slave  Java - 7 (7.0.49)  Subversion Tagging Plugin version: 1.18  Installed Jenkins directly using installer  tried multiple browsers Chrome, Firefox 
 
 
 

Labels:
 

 plugin 2.0 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Devesh Kumar 
 
 
 
 
 
 
 
 
 
 
I recently upgraded my Jenkins from 1.543 to Jenkins 2.1 and Subversion Tagging Plugin automatically got upgraded from 1.17 to 1.18. However the SVN tagging fails with below exception, I reverted the plugin back to 

[JIRA] [build-name-setter-plugin] (JENKINS-34512) error in build-name-setter plugin - Set build name

2016-05-02 Thread devesh....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Devesh Kumar edited a comment on  JENKINS-34512 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: error in build-name-setter plugin - Set build name  
 
 
 
 
 
 
 
 
 
 Pasting the entire job configuration: {quote}   false180100-1-1    *MASKED*.infinityfalse  falsefalsetrue  false  false  falseH 8,12,16,20 * * 1-5  falsefalse    MSBuild 4.0  FinanceBrokerServices\FinanceBroker.sln  /t:Clean,Rebuild /p:Configuration=Release,platform=Any CPU  true  false  false  *.xml  false  false  false  false    checkstyle  checkstyle  10  999  999  false  codenarc  codenarc  10  999  999  false  cpd  cpd  10  999  999  false  cpplint  cpplint  10  999  999  false  csslint  csslint  10  999  999  false  findbugs  findbugs  10  999  999  false  fxcop  fxcop  10  999  999  false  gendarme  gendarme  10  999  999  false  jcreport  jcreport  10  999  999  false  jslint  jslint  10  999  999  false  pep8  pep8  10  999  999  false  perlcritic  perlcritic  10  999  999  false  pmd  pmd  10  999  999  false  pylint  pylint  10  999  999  false  simian  simian  10  999  999  false  stylecop  stylecop  10  999  999  false100default  

[JIRA] [build-name-setter-plugin] (JENKINS-34512) error in build-name-setter plugin - Set build name

2016-05-02 Thread devesh....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Devesh Kumar commented on  JENKINS-34512 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: error in build-name-setter plugin - Set build name  
 
 
 
 
 
 
 
 
 
 
Pasting the entire job configuration: 

false180 100 -1 -1MASKED . infinity false false false  true false false false   H 8,12,16,20 * * 1-5 false   false   MSBuild 4.0 FinanceBrokerServices\FinanceBroker.sln /t:Clean,Rebuild /p:Configuration=Release,platform="Any CPU" true false false *.xml false false false false   checkstyle  checkstyle 10 999 999 false codenarc  codenarc 10 999 999 false cpd  cpd 10 999 999 false cpplint  cpplint 10 999 999 false csslint  csslint 10 999 999 false findbugs  findbugs 10 999 999 false fxcop  fxcop 10 999 999 false gendarme  gendarme 10 999 999 false jcreport  jcreport 10 999 999 false jslint  jslint 10 999 999 false pep8  pep8 10 999 999 false perlcritic  perlcritic 10 999 999 false pmd  pmd 10 999 999 false pylint  pylint 10 999 999 false simian  simian 10 999 999 false stylecop  stylecop 10 999 999 false 100   default$DEFAULT_RECIPIENTS $PROJECT_DEFAULT_SUBJECT $PROJECT_DEFAULT_CONTENT   false false $PROJECT_DEFAULT_REPLYTO project  $PROJECT_DEFAULT_SUBJECT $PROJECT_DEFAULT_CONTENT   false false $PROJECT_DEFAULT_REPLYTO projectdefault $DEFAULT_SUBJECT $DEFAULT_CONTENT  $DEFAULT_PRESEND_SCRIPT  false false  false false  #$ 

Unknown macro: {BUILD_NUMBER} 
 
 true true   
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-name-setter-plugin] (JENKINS-34512) error in build-name-setter plugin - Set build name

2016-04-29 Thread devesh....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Devesh Kumar created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34512 
 
 
 
  error in build-name-setter plugin - Set build name  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Lev Mishin 
 
 
 

Components:
 

 build-name-setter-plugin 
 
 
 

Created:
 

 2016/Apr/29 2:56 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Devesh Kumar 
 
 
 
 
 
 
 
 
 
 
I recently upgraded my Jenkins from 1.543 to Jenkins 2 and build-name-setter plugin automatically got upgraded from 1.3 to 1.6.5. However the build fails, here are the logs: 
16:52:02 Set build name. 16:52:02 New build name is '#553' 16:52:02 Variable with name 'BUILD_DISPLAY_NAME' already exists, current value: '#553', new value: '#553' 
OS: Windows Server 2008 R2 Ent./64 bit Jenkins - 2.0 - Only Master no Slave Java - 7 (7_49) build-name-setter-plugin version: 1.6.5 Installed Jenkins directly using installer tried multiple browsers Chrome, Firefox 
I reverted the plugin to old version 1.3 and it works well with Jenkins 2.0. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment